How to interpret this chart: small number good, big number bad.
We've known for a few days that we probably have a memory leak, and that it's probably impacting site performance, but we hadn't really seen it For Real until this.
At around 11:15, we did a deploy which obviously restarted all our server processes. The fact that there's an extremely visible cliff there told me that yeah we gotta actually fix this. Or at least mask over the fact that we are unclear on what's causing it.
So this morning I took the coward's way out and shipped a cron job that will simply restart the server processes one at a time every 4 (subject to change) hours. foolproof. I already tested it and it worked perfectly. You love to see it.
This should improve some of our resource scheduling issues as well as site performance overall, which is a huge W b/c that saves us money.
that's all thanks for reading. also i kinda want to do this sort of post more often so lmk if you want to see that.
“There’s been great tricks that [Xbox] taught us,” Howard said. “My favorite one in Morrowind is, if you’re running low on memory, you can reboot the original Xbox and the user can’t tell. You can throw, like, a screen up. When Morrowind loads sometimes, you get a very long load. That’s us rebooting the Xbox. That was like a hail Mary.” https://kotaku.com/morrowind-completely-rebooted-your-xbox-during-some-loa-1845158550
