Skip to end of banner
Go to start of banner

DRAFT - NMIS - Optimize nmis8/var For Speed - RAM Disk

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

« Previous Version 3 Next »

Overview

Some customers may benefit by moving files that NMIS reads/writes to very often to a RAM Disk.  We have seen this improve performance on pollers that have shared storage and 2,000+ nodes provisioned.  The concept is that NMIS will be able to read/write to RAM faster than the shared storage.  Most of these files that NMIS touches very often are found in the nmis8/var directory.

Procedure

Step #1 - Determine Space Required

There are two questions that quickly come to mind:

  • How big should the RAM disk be?
  • How much RAM is available?

Check how much space nmis8/var is currently using; minus the nmis8/var/events directory.  We will keep the nmis8/var/events directory on a hard drive because it contains stateful event history; we don't want to loose these if the server is rebooted. 

  • No labels