-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
repos/pulls api take long time for large repos #31492
Comments
Facing the same issue while using Postgres. |
another poke, i'm facing the same issue on projects.blenders.org tracker, but rather than a long wait and still giving the data, their server just gives a running a |
Can you post the link? |
I'm not entirely sure what you're asking? the link to what? the fact shortstat somehow runs i got from the opening post in this ticket, the failing call on the blender server you can repro with if it's something else you're looking for happy to help but you're gonna have to be a bit more specific :) |
I was curious what these long running commands look like, so I copied a few and ran them locally. I had to run |
It's very strange because the web request https://projects.blender.org/blender/blender/pulls is very fast. If you can provide some logs about this API requests, that's better. |
If the loading time increases for all "old" pages, it seems to be a SQL index or optimizer problem. In many cases |
I'm not in control of that server, but i'll prod blender devops, they should be able to dig up whatever you need, could be a few days though, hang tight! |
The following logging is what I could drum up:
|
Can you also give more context logs of API requests, your previous log lost some details? |
If there is performance problem, maybe you could refer to the diagnosis tool to collect performance profiles. Steps:
|
And if the performance is related to SQL, you could enable SQL logs to see what happens: https://docs.gitea.com/help/support (LOG_SQL) |
I'm working on this one. |
#32680 is ready to review. |
Description
I'm working with renovate which makes calls to
api/v1/repos/org/repo/pulls?state=all&sort=recentupdate&page=[page]
. At pages 8+ the requests take a long time. Looking at htop it's because the git diff command is blocking.This is likely because my repo had a large restructure, loading the diffs on the gitea web app is also very slow.
Is there any way to cache diffs or any config I can use to speed them up? My current workaround is to set the request timeout to 5 min in renovate
Gitea Version
1.22.0
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
https://gist.github.com/GammaGames/b1ae6715c8a66da638ee181ed6f93da1
Screenshots
Git Version
No response
Operating System
No response
How are you running Gitea?
Docker compose:
Database
SQLite
The text was updated successfully, but these errors were encountered: