[performance] Listing repositories is slow #11364

Closed
opened 2025-11-02 09:35:34 -06:00 by GiteaMirror · 6 comments
Owner

Originally created by @KazzmanK on GitHub (Jul 29, 2023).

Description

Request to
/repo/search?sort=updated&order=desc&uid=3&team_id=undefined&q=&page=1&limit=100&mode=&archived=false

on dashboard page (http://root_path), right pane, takes almost 5 seconds for 50 repositories exists

Database - sqlite

At the same time same repository list on http://root_path/organization appears instantly

Screenshots

none

Gitea Version

1.20.1

Can you reproduce the bug on the Gitea demo site?

No

Operating System

Windows server 10.0

Browser Version

113

Originally created by @KazzmanK on GitHub (Jul 29, 2023). ### Description Request to /repo/search?sort=updated&order=desc&uid=3&team_id=undefined&q=&page=1&limit=100&mode=&archived=false on dashboard page (http://root_path), right pane, takes almost 5 seconds for 50 repositories exists Database - sqlite At the same time same repository list on http://root_path/organization appears instantly ### Screenshots none ### Gitea Version 1.20.1 ### Can you reproduce the bug on the Gitea demo site? No ### Operating System Windows server 10.0 ### Browser Version 113
GiteaMirror added the performance/speedtopic/ui labels 2025-11-02 09:35:34 -06:00
Author
Owner

@KazzmanK commented on GitHub (Jul 29, 2023):

Oh, looks like for every repo 3 git commands are executed. Looks like information from database is not sufficient to display repo list. But in Json returned by rest method seems does not contains any special data.

@KazzmanK commented on GitHub (Jul 29, 2023): Oh, looks like for every repo 3 git commands are executed. Looks like information from database is not sufficient to display repo list. But in Json returned by rest method seems does not contains any special data.
Author
Owner

@KazzmanK commented on GitHub (Jul 29, 2023):

It is not clear, why here, in "https://root_path", after "SearchRepositoryByCondition" git commands are executed, but on "https://root_path/Organization" after the same "SearchRepositoryByCondition" - no git commands are executed and pageload is instant.

@KazzmanK commented on GitHub (Jul 29, 2023): It is not clear, why here, in "https://root_path", after "SearchRepositoryByCondition" git commands are executed, but on "https://root_path/Organization" after the same "SearchRepositoryByCondition" - no git commands are executed and pageload is instant.
Author
Owner

@lunny commented on GitHub (Jul 30, 2023):

This issue comes from #24638 in v1.20 and should be resolved by #22743 in v1.21

@lunny commented on GitHub (Jul 30, 2023): This issue comes from #24638 in v1.20 and should be resolved by #22743 in v1.21
Author
Owner

@Sebazzz commented on GitHub (Sep 11, 2023):

Yes, I also ran into this after upgrading v1.19 to v1.20.4. Glad a fix is inbound!

@Sebazzz commented on GitHub (Sep 11, 2023): Yes, I also ran into this after upgrading v1.19 to v1.20.4. Glad a fix is inbound!
Author
Owner

@lunny commented on GitHub (Dec 5, 2024):

I think this has been resolved. Please feel free to reopen if it is still a problem.

@lunny commented on GitHub (Dec 5, 2024): I think this has been resolved. Please feel free to reopen if it is still a problem.
Author
Owner

@Sebazzz commented on GitHub (Dec 5, 2024):

Yes, though also simply reorganizing indices in MSSQL also helped!

@Sebazzz commented on GitHub (Dec 5, 2024): Yes, though also simply reorganizing indices in MSSQL also helped!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#11364