News for hackers. Stuff that matters.
Re:Linux Performance: Why You Should Almost Always Add Swap ... by ausjke on Monday December 18, 2017 @09:33AM (#15951823)
indeed on ubuntu 16.04 64bit, when my chrome has 20+ tabs, some new tab could trigger a memory thrashing, that uses up all the memory and eats up a few GB disk, cpu load jumps up to 10x, the computer basically becomes unusable.

i would rather a OOM kill the chrome process in this case, it wastes less time on me, a re-open of chrome will keep all the histories anyways.

also on embedded system where the RAM is fairly limited, and no hard drive attached, and its storage is measured by MB instead of GB, you simply can not have the swap partition.

I want to run the system without swap actually.

Re:Linux Performance: Why You Should Almost Always Add Swap ... by warrenm on Monday December 18, 2017 @10:39AM (#15952307)
>when my chrome has 20+ tabs

That's not a swap problem, that's a Chrome problem.

Re:Linux Performance: Why You Should Almost Always Add Swap ... by AstralStorm on Tuesday December 19, 2017 @01:46AM (#15958268)
It is a swap problem. Swap is supposed to make things work and not stop.

I suppose this is actually a problem of Linux optimistic malloc policy.