is this Little Bobby Tables?
this post was submitted on 16 Mar 2026
306 points (96.6% liked)
Selfhosted
56953 readers
2282 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
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.
To "fix" the memory leak, just restart your server every day with a cron job /s
My actual "solution" was to do nothing and just let Kubernetes restart it when it OOMs 😅
Cron job too complicated, just buy one of those timed light controllers to power off the server every night for an hour.