5 ms·

This sounds as if it is a serious issue and should be fixed. Is there a bug report about it?

• lolc 9y ago
  This is due to memory overcommit, it's a performance feature. You can turn it off.
  • kevin_nisbet 9y ago
    Interesting, I sort of remember an interaction with NUMA as well. I don't believe this is a bug, just a miss-understanding of the way the underlying system works. From what I remember when swapiness is 0, there are lots of reports of processes that use more than a single NUMA node worth of memory getting killed by the OOM killer, even with plenty of free RAM available. I unfortunately don't remember the details, but this prevented the memory from being able to be allocated to the additional node. I've heard of this mostly with mysql, where it's common to have a big server with lots of RAM, but a single large process that uses most of the system RAM. The way we got around this, was by setting the process to allocate interleaved among the NUMA nodes. I'll have to dig into the overcommit.
• warrenm 9y ago
  It's not a serious issue at all. It's intentional.