-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
[Summary] Loading user dashboard too slow #31698
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
performance/speed
performance issues with slow downs
type/summary
This issue aggregates a bunch of other issues
Comments
#32110 should resolve the problem. |
Hope it works. |
#32127 should resolve the problem for most Gitea instances. |
Still got report after upgrade to the latest version. |
I think we can close this one and leave #29769 open. |
update 1.23.3 home page also too slow
|
GiteaBot
pushed a commit
to GiteaBot/gitea
that referenced
this issue
Feb 24, 2025
Fix go-gitea#33582 Fix go-gitea#31698 When a user login, the dashboard should load all feed belongs to him with no any conditions. The complicated conditions should be applied only for another user view this user's profile.
lunny
added a commit
that referenced
this issue
Feb 25, 2025
Backport #33686 by @lunny Fix #33582 Fix #31698 When a user login, the dashboard should load all feed belongs to him with no any conditions. The complicated conditions should be applied only for another user view this user's profile. Co-authored-by: Lunny Xiao <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
performance/speed
performance issues with slow downs
type/summary
This issue aggregates a bunch of other issues
Feature Description
We have received may reports about loading user dashboard too slow.
Please discuss/report related/similar issues (only the user dashboard, other pages are fine) in this summary, and avoid creating more and more.
Although these reports maybe caused by different reasons, I think it is better to have a summary about this issue.
@lunny
Can you pin this issue on the top?
Opening:
Closed:
Screenshots
No response
The text was updated successfully, but these errors were encountered: