Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> First off, this is exactly how systemd-oomd is supposed to behave under memory pressure. The documentation is specific on this; systemd-oomd itself says:

> > [...] If the configured limits are exceeded, systemd-oomd will select a cgroup to terminate, and send SIGKILL to all processes in it. [...]

> By having the user@.service template be enrolled in systemd-oomd, Fedora made the cgroup that systemd-oomd would select to be killed be all of your processes (across all of your sessions, if you have more than one). ...

Maybe *Fedora* has fixed or improved in the last 4 years. Or maybe they don't run Fedora.

 help



One thing Fedora does now, is use zram.

In my experience it works really well. I wonder why my computer is a bit sluggish, and find out I have several gigs in zram.

If that was in swap on a disk, it would be really painful.


If it were swap on disk fronted by zswap, it'd be even better ;)

I'm a Fedora developer and I can assure you that Fedora's behaviour when it runs out of memory is still terrible.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: