/
Reducing a Server's Memory Footprint when OMK applications are installed

Reducing a Server's Memory Footprint when OMK applications are installed

Apr 20, 2022

 

Exercise caution while editing /usr/local/omk/conf/opCommon.nmis, /usr/local/omk/conf/opCommon.json or /etc/mongod.conf; if a syntax error is induced all OMK applications will cease to function.

Check out How to make configuration changes to opCommon.nmis and other files for some more details on best practices for modifying the configuration file.

Reducing a Server's Memory Footprint


NMIS 8

NMIS 9

Consider using zram or zswap to extend available memory, with default settings, provided the server does not have high CPU usage.

Advantages of zram

  • An advantage of zram is that it does not need to be backed by an appropriately sized swap space - and this makes it easier to configure and maintain during the lifecycle of the server.

  • Another advantage of zram is that it is more likely to function in low memory environments whereas zswap should not be used when the server  has less than 1GB RAM.

  • Another advantage of zram is that I've not encountered a server kernel that is not supporting it (zram), whereas I have encountered this with zswap on occasion.

Disadvantages of zram


Setting cacheSizeGB appropriately when MongoDB table type is wiredtiger (the default)

If your MongoDB installation is using table type wiredtiger, please read
https://docs.mongodb.com/manual/reference/configuration-options/#storage.wiredTiger.engineConfig.cacheSizeGB

 

Related Topics