What does HackerNews think of prelockd?
Lock executables and shared libraries in memory to improve system responsiveness under low-memory conditions
Language:
Python
This may or may not preserve your desktop and other important applications in an OOM situation. https://github.com/hakavlad/prelockd
I've heard some good results with it and the applications locked in memory is configurable.
I wonder how does this compare to the state of the art solutions from the author of Nohang:
https://github.com/hakavlad/prelockd
https://github.com/hakavlad/memavaild
https://github.com/hakavlad/le9-patch
in terms of % saved memory or % prevented hangs/OOM / lost base runtime performance
How will systemd-oomd communicate to the user?
I was using https://github.com/hakavlad/nohang
And it sent notification signaling to save your work before the application X will be killed. (I always wanted a way to click somewhere on the notification to prevent nohand from killing it when unwanted)
Also nohang use PSI data does oomd does it too?
Finally the author of nohang is working on arguably superior solutions: https://github.com/hakavlad/prelockd https://github.com/hakavlad/memavaild https://github.com/hakavlad/le9-patch It's unfortunate that systemd has chosen to integrate an inferior solution
Look at the new tools:
https://github.com/hakavlad/prelockd
https://github.com/hakavlad/memavaild
It can greatly improve responsiveness. Demo:
https://youtu.be/QquulJ06dAo - playing supertux + 12 `tail /dev/zero` in background
https://youtu.be/DsXEWvq60Rw - `tail /dev/zero`, swap on HDD, memavaild, no freezes