3 ms·

Gitea is very easy to use, but I find the Activity feature is a little slow. I experienced the "Try Gitea" service and migrated our TiDB repo https://github.co

Gitea is very easy to use, but I find the Activity feature is a little slow. I experienced the "Try Gitea" service and migrated our TiDB repo https://github.com/pingcap/tidb https://github.com/pingcap/tidb to it. When I clicked the Activity tab and selected "1 year" period, I found the page loading was so slow, nearly 90s. And I also found that this Activity doesn't have a Cache, I re-selected "1 year" again, and the page loading was nearly the same time. I guess Gitea uses git command to traverse all the logs for the period every time. Maybe it can use a database to speed up, or like Github only provide at max "1 month" period.

capableweb 4y ago
Could just be because the "Try Gitea" service is just a test deployment, staging environment if you will. I don't think it's optimized in any way at all. Trying to same on Codeberg, which is a production environment of Gitea, the loading time of the "Activity" page for Codeberg/gitea seems to take ~5 seconds for me. It still seems to lack any sort of caching, but at least it's relatively fast. See https://codeberg.org/Codeberg/gitea/activity/yearly https://codeberg.org/Codeberg/gitea/activity/yearly (people might want to be careful hitting that URL over-and-over, in case we ddos the Codeberg folks :/ )