gitea: Slow to open a repo if there’s many branches in it
- Gitea version (or commit ref): 1.13.0
- Git version: git 2.29.2.windows
- Operating system: Windows 10 1809
- Database (use
[x]):- PostgreSQL
- MySQL
- MSSQL
- SQLite
- Can you reproduce the bug at https://try.gitea.io:
- Didn’t really try
- Yes (provide example URL)
- No
- Log gist:
Description
The title may be a bit misleading.
I was building a local mirror of PyTorch manually using git push —mirror. And I found that opening the repo is exceptionally slow (~11 seconds). I also built a clone of gitea itself and the time to open the repo is reasonable (~2 seconds).
I think the reason is that PyTorch has over 4000 branches in it.
Screenshots
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 2
- Comments: 28 (26 by maintainers)
Commits related to this issue
- Sync branches into databases (#22743) Related #14180 Related #25233 Related #22639 Close #19786 Related #12763 This PR will change all the branches retrieve method from reading git data to ... — committed to go-gitea/gitea by lunny a year ago
- Use frontend fetch for branch dropdown component (#25719) - Send request to get branch/tag list, use loading icon when waiting for response. - Only fetch when the first time branch/tag list shows.... — committed to go-gitea/gitea by HesterG a year ago
I agree, this would also help for PR creating page where branches need to be selected and other places where we currently show all branches to make that dropdown to show only top branches and make it async searchable