Skip to end of banner
Go to start of banner

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

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

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

  • ABI 1 (NMIS 8)
    • In omk/conf/opCommon.nmis, omkd_workers is set at 10. Try reducing this number to 5 and then restart the omkd service.
      If you THEN find YOU need more omkd_workers, increment this value by one and test again until you get to a suitable value for omkd_workers
  • ABI 2 (NMIS 9)
    • In omk/conf/opCommon.json, omkd_workers is set at 10. Try reducing this number to 5 and then restart the omkd service.
      If you THEN find YOU need more omkd_workers, increment this value by one and test again until you get to a suitable value for omkd_workers
  • The default MongoDB table type is wiredtiger.
    If your MongoDB installation is using table type wiredtiger, please read
    https://docs.mongodb.com/manual/reference/configuration-options/#storage.wiredTiger.engineConfig.cacheSizeGB
    • Consider setting cacheSizeGB appropriately taking into consideration the memory requirements of other processes running on this box.
      With default mongod settings, a box with 16GB memory may use more than 7GB of memory for cacheSizeGB.
      This may be too much considering the box may be running NMIS and OMK Applications too.
      • You can check how much memory mongod is using for this cache in the mongod.log where it is provided in MB, for example:
        • STORAGE [initandlisten] wiredtiger_open config: create,cache_size=7414M,


  • No labels