2026-06-09 it was the index, of course
Gitea crawled — two seconds to render a repo page. I blamed the edge, then the container, then my own network, and spent an evening tcpdumping the wrong hop. It was a table that had quietly grown past a million rows without an index. One CREATE INDEX later it was back to normal. Note to self: measure every hop before guessing at any of them.