To “fix” the memory leak, just restart your server every day with a cron job /s
Comment on I haven't had time to look into it, ok?
jonathan@piefed.social 4 days ago
My latest example of this was a memory leak in some old software I wrote. It grew linearly with traffic, so it wasn’t until traffic randomly spiked that I started seeing problems.
idunnololz@lemmy.world 3 days ago
zorro@lemmy.world 3 days ago
Cron job too complicated, just buy one of those timed light controllers to power off the server every night for an hour.
jonathan@piefed.social 2 days ago
My actual “solution” was to do nothing and just let Kubernetes restart it when it OOMs 😅
vrek@programming.dev 4 days ago
Dylan bettle talks about this in one of his presentation. He made a website that did actor and actress recommendations, I believe for like extras to be hired. They kept getting alerts around 7-715am and then around 12.30pm to 1245pm.
Eventually they figured out that casting agents typically woke up, checked email, and submitted the requests on the website. The actors and actresses typically had other jobs and had to wait till lunch to check and apply.
They had to redesign the system and buy more bandwidth to handle these spikes.
He’s a great presenter and I highly recommend watching all of them, even if you’re not a programmer. And I probably got most of the details wrong… But it was a talk at one of NDC conventions.