Domino server crashed for some reason and you would like to determine how much physical memory is allocated to Domino Shared Memory. Usually one would want to focus on this if they are seeing insufficient memory errors.
Insufficient Memory error seen on the Domino console.
This is mostly seen on a 32bit Operating system due to the max 2GB limit of addressable space. When this 2GBs of memory is exhausted Domino will crash being it can not allocate more memory that it needs.
If the Domino Server crashed you can open the nsd file and then search for Static-DPOOL. The first hit should be for Domino Shared Memory but double check that the header says Shared Memory Stats :: (Shared). Cross reference Static-DPOOL with SIZE and this will show you how much physical memory is allocated to Domino Shared Memory. Here is an example where Domino Shared Memory is using 1.55GBs of memory:
If the Domino server is actively up and running you can not just use Task Manager to see memory usage. Some of the processes may show really high numbers. This is because and Domino server task using Domino shared memory will show its private size plus the Domino shared memory. So if Domino shared memory is 1.2GBs and your app is using 200MBs it will show in Task Manager as using 1.4GBs. To see how much of that is actually shared memory in Task Manager you would need to select View/Select Columns and then check next to Virtual Memory Size. A better tool to use is VMMap which you can get for free from Microsoft at the following location http://technet.microsoft.com/en-us/sysinternals/bb842062
Imported Document ID: TECH150485
Subscribing will provide email updates when this Article is updated. Login is required.