Memory usage plotted over time. Sawtooth pattern on the left, followed by a noticable drop in memory use and a much slower, gradual increase.

Notices where this attachment appears

1. Embed this notice
   Ayo (ayo@lonely.town)'s status on Friday, 09-May-2025 22:05:13 JST Ayo

   I've always had an automatic kill+restart for VNDB backend processes when they've processed between 5k-10k requests. A good strategy in general, because it's fairly common for Perl processes to accumulate memory over time.

   Now that I'm using prepared statement caching, it seems beneficial to keep the backend processes alive for a bit longer, so I started hunting for memory leaks that I could control. Sure enough, found an accidental reference cycle that was responsible for most of the leaking.
   https://g.blicky.net/vndb.git/commit/?id=0d597dd43e1fdb4ff36e2c405825a763942d6d3f

   There's probably a few more subtle leaks, but they're not easy to track down...