> vm.swappiness = 0 The kernel will swap only to avoid an out of memory condition, when free memory will be below vm.min_free_kbytes limit. This is not the cas

> vm.swappiness = 0 The kernel will swap only to avoid an out of memory condition, when free memory will be below vm.min_free_kbytes limit. This is not the case. It used to be the case, but changed in kernel version 3.5-rc1 (2012 ish) There was a discussion about this on HN a few weeks ago: https://news.ycombinator.com/item?id=13511086 https://news.ycombinator.com/item?id=13511086 And there's a blog post on the percona website about how this rather bizarre change bit them: https://www.percona.com/blog/2014/04/28/oom-relation-vm-swappiness0-new-kernel/ https://www.percona.com/blog/2014/04/28/oom-relation-vm-swap... I call it bizarre because (as I wrote in that other HN thread) a) it changed the behaviour of lots of production systems in a surprising way, and b) if you want to ensure your processes never swap you already had the option to not have a swap file or partition.