News for hackers. Stuff that matters.

A comment on Linux Performance: Why You Should Almost Always Add Swap Space. Parent comment

Re:Linux Performance: Why You Should Almost Always Add Swap ... by Dylan16807 on Monday December 18, 2017 @10:16AM (#15952158)
> I'd rather have the server reboot than have some random process crash and leave the system in a potentially broken state.

Set the OOM killer to trigger a reboot? Crawling to a swapping halt is the worst of both worlds, it's like a full system crash but the server never comes back.

[ Parent | on HN ]
Re:Linux Performance: Why You Should Almost Always Add Swap ... by AstralStorm on Tuesday December 19, 2017 @01:49AM (#15958277)
Set overcommit policy and malloc would just fail, which is handled in mysql and would abort the query instead of invoking oom killer.

And a crashing service should get restarted, involving journal file recovery which is consistent state.

[ Parent | on HN ]
Re:Linux Performance: Why You Should Almost Always Add Swap ... by Dylan16807 on Tuesday December 19, 2017 @05:29AM (#15959200)
> Set overcommit policy and malloc would just fail, which is handled in mysql and would abort the query instead of invoking oom killer.

So many things depend on so many gigabytes of overcommit, that seems like a pretty bad way to go about it in the general case.

> And a crashing service should get restarted, involving journal file recovery which is consistent state.

I think you're agreeing with me with this sentence?

[ Parent | on HN ]