https://bugzilla.wikimedia.org/show_bug.cgi?id=51943
Marc A. Pelletier <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #1 from Marc A. Pelletier <[email protected]> --- Not an issue except for processes that map hardware, which nobody should be running on execution hosts (your example, with X, is illustrative: it includes the mmap() of video memory) The vmem usage includes the the data and executable of the process itself, of course, but also include every shared library that is bound at runtime. In practice, it is the maximum amount of memory it /could/ use were it the only one using those shared libraries -- and therefore the correct amount to check against to prevent overcommiting. This is why the execution nodes were given a generous amount of swap; it guarantees we won't overcommit yet allows mostly efficient usage of the actual ram. "(for example process that needs 2gb of resident memory, may have 40gb vmem usage in linux kernel, even if it makes no sense)", on the other hand, is simply wrong. The overhead from shared libraries is fixed. -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
