Enable Content-Encoding: gzip to improve forgeperf.org benchmark scores
The benchmarks at https://forgeperf.org/ (operated by SourceHut) show a poor result for Codeberg.
I think it is not entirely representative as Codeberg certainly seems quite fast to me (does the
lighthouse test script preserve cached resources between tested URLs??), but, there are some easy wins that can be done.
Codeberg has put gitea directly internet-facing, but an nginx layer can be used to add gzip support. Or perhaps it could be patched into gitea (e.g. via the https://github.com/nytimes/gziphandler Go package).
Thanks for bringing this up!
We have enabled gzip compression now in haproxy for:
- text/plain text/xml
Their lighthouse test simulates a mobile networks with ~1.6MBit/s, because the SourceHut founder thinks it is a realistic scenario for a developer to work with a mobile network.
So it is (at least for some benchmarks) pretty clear that a forge that looks almost identical to about:blank would win here 😆
Anyway, at least https://forgeperf.org/ and your comment hepled us to improve! 👍
Codeberg has put gitea directly internet-facing
This is incorrect. It is behind a haproxy which is responsible for ssl and http2, and since today also does compression.
Deleting a branch is permanent. It CANNOT be undone. Continue?