Improve federated avatars DNS lookups #522

New Issue

GiteaMirror · 2025-11-02T03:26:37-06:00

GiteaMirror commented

2025-11-02 03:26:37 -06:00

Originally created by @strk on GitHub (Mar 16, 2017).

At the moment enabling FEDERATED_AVATARS results in some delays whenever the server has to provide the URL to the avatar of users whose federated avatar url is not found in the ad-hoc cache (which has 1 day of lifetime).

While this may not be a big deal in a page with a single user, explore/users page can show many users and if these have emails with many different domains the delay sums up until browser possibly times out.

The situation may be improved in various ways:

Make sure multiple thread asking for the same domain lookup all queue so that a single lookup is ever performed (but I'd think the operating system should already being taking care of this)
Always perform the lookup in the background and save the result in db tables

In any case it would be useful to document the problem with the setting that enables these.

Originally created by @strk on GitHub (Mar 16, 2017). At the moment enabling FEDERATED_AVATARS results in some delays whenever the server has to provide the URL to the avatar of users whose federated avatar url is not found in the ad-hoc cache (which has 1 day of lifetime). While this may not be a big deal in a page with a single user, explore/users page can show many users and if these have emails with many different domains the delay sums up until browser possibly times out. The situation may be improved in various ways: 1. Make sure multiple thread asking for the same domain lookup all queue so that a single lookup is ever performed (but I'd think the operating system should already being taking care of this) 2. Always perform the lookup in the background and save the result in db tables In any case it would be useful to document the problem with the setting that enables these.

GiteaMirror added the type/enhancement issue/stale labels 2025-11-02 03:26:37 -06:00

GiteaMirror closed this issue

2025-11-02 03:26:38 -06:00

GiteaMirror commented

2025-11-02 03:26:38 -06:00

@stale[bot] commented on GitHub (Feb 16, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Feb 16, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

GiteaMirror commented

2025-11-02 03:26:39 -06:00

@stale[bot] commented on GitHub (Mar 2, 2019):

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale[bot] commented on GitHub (Mar 2, 2019): This issue has been automatically closed because of inactivity. You can re-open it if needed.

GiteaMirror referenced this issue

2025-11-02 09:20:19 -06:00

[Actions] Support concurrency syntax #10862

GiteaMirror referenced this issue

2025-11-02 09:20:19 -06:00

[Actions] Support concurrency syntax #10862

GiteaMirror referenced this issue