3 ms·
die on run out of memory is a bad policy for a userspace server. Seen some hairy production incidents with that, basically solution is piss off customers until
by teknopaul 6y ago
die on run out of memory is a bad policy for a userspace server. Seen some hairy production incidents with that, basically solution is piss off customers until they stop coming back.
action on run out of memory should be finish up currently running work and hold off new stuff until you have resources, not die and start to reprocess the thundering herd.
When you run out of memory last thing you want to do is empty your hot caches.
- bronson 6y agoYou’re out of memory. Every possible cache has already been freed. Unless your app is faking it’s own caching, in which case it might be contributing to the problem.
- angry_octet 6y agoIt's quite possible that an app is holding onto data that can be flushed, at the expense of future database lookups, session negotiations, etc. Without a proper mechanism in the kernel it is hard to manage memory pressure.
- nabla9 6y agoIf that would be important you would disable overcommit in Linux. If you didn't do that, it's probably because it's good tradeoff that saves resource.