Chester Liu
Chester Liu
年轻真好+1
So I did a little debugging with Gitea code and found that the reason is the number of branches.
The root cause of this seem to be `git show-ref` used by gitea becomes very slow for a repo like PyTorch which have 4000+ branches
I’m new to golang. I’ll try pprof later. Based on my debugging using logging, I found most of the time was spent in `GetTags` & `GetBranches` in `repoAssginment`. This is...
I was using the latest master on my mac. And it is still not good. I also delibrately tried building it with 'gogit' flag. But changing 'show-ref' to 'branch/tag' without...
On Linux there's buff/cache, which will aggresively cache everything used on the file system. So i think on Linux it should be better. But still, 'show-ref' feels like an unnecessary...
The one with 4000+ branches on the same page? TBH I never once successfully opened the page until I added pagination myself. The repo homepage feels considerably slow to me,...
Interesting. That explains why using 'branch/tag' still feels slower, comparing to repos that have a smaller size. Way to go, PyTorch.
@zeripath I was joking about PyTorch. I'm glad my findings turned out to be useful to gitea.
So I was trying pprof but got something like this: ``` (pprof) top10 Showing nodes accounting for 1110ms, 70.70% of 1570ms total Showing top 10 nodes out of 328 flat...