Re:Improved default settings for Linux machines
by angry_octet on Tuesday June 24, 2014 @10:23PM
(#7941920)
An even better idea for developers is to reduce limits (memory, PIDs, file handles) and start triggering those rarely-used (or non-existent) error handling code paths.
Also, I think I would prefer process sbrk failure to OOM killer activation. So setting vm/overcommit_memory=2, overcommit ratio to 80%, a decent swap size, and code actually handling errors. IE consistency versus randomness.
Re:Improved default settings for Linux machines
by mje__ on Tuesday June 24, 2014 @11:50PM
(#7942148)
Agreed. The last thing you want is to have to debug those weird "it worked on my desktop" issues that come from having a really weirdly configured system
Also, I think I would prefer process sbrk failure to OOM killer activation. So setting vm/overcommit_memory=2, overcommit ratio to 80%, a decent swap size, and code actually handling errors. IE consistency versus randomness.
Not that randomness is bad for testing, cf Chaos Monkey: https://github.com/Netflix/SimianArmy/wiki/Chaos-Monkey