Valdis.Kletnieks@xxxxxx wrote:
A better bet would be a patch that allowed you to set the maximum RSS size for
the process so it can basically thrash itself while leaving enough memory for
everybody else (and yes, I *know* how this can be self-defeating if the
thrashing app then increases the total I/O consumed to be higher than the I/O
bandwidth available - the point is that it's probably the high RSS value for
his application causing OTHER things to thrash that's the root cause of his
performance problem).
Or you could use "ulimit -m" to set the RSS, of course.