Memory-management optimization with DAMON

Memory-management optimization with DAMON

we identified frequently accessed memory regions in each workload based on the DAMON results and protected them with mlock() system calls. The optimized versions consistently show speedup (2.55x in best case, 1.65x in average) under memory pressure.

If feel like "under memory pressure" should be emphasised here. Yes, if you're low on memory and the system is needing to swap, then preventing some regions of memory from being swapped could certainly improve the performance... of that particular application.

However, if you're low on memory and the system is needing to swap, then preventing some regions of memory from being swapped is probably going to have an adverse effect on all the other applications on the system.

That kind of speedup certainly justifies spending some time looking at a process's memory patterns. It would be even nicer, though, if the kernel could do that work itself — that is what a memory-management subsystem is supposed to be for, after all.

I feel like the memory management subsystem should be for making the system as fair as possible?