Troubleshooting Remote Loader and Driver Memory Usage on Windows using PerfMon

  • 3658843
  • 30-Nov-2007
  • 26-Apr-2012

Environment

Novell Identity Manager 3.6
Novell Identity Manager 3.5.1
Novell Identity Manager 3.5
Novell Identity Manager 3.0
Novell Identity Manager - Remote Loader
Novell Identity Manager - Password Synchronization

Situation

Remote Loader on Windows using up too much memory and/or crashing. Is there a way to track the memory usage of Remote Loader and the driver?

Resolution

Launch PerfMon, go to Performance Logs and alerts, on Counter Logs, right click and add "New Log settings..." give it a representative name, click Add Counters, select the destination computer (the local or a remote).
In performance object, pick Process. Then pick the following items for the 'Select counters from list' option:
  • Thread Count
  • Working Set
  • Virtual Bytes
  • Private Bytes
  • Pool Nonpaged Bytes
  • Pool Paged Bytes
Now in the Select Instance from list, pick dirxml_remote . Press Add for each of the counters mentioned above. (make sure it's the dirxml_remote counters and not the _Total values you are getting).

Once this is done, please run this until the next Remote Loader crash happens, then save the log file. At that point, contact Novell Support for further help.

Additional Information

Below is an explanation of each counter mentioned above:

Thread Count
The number of threads currently active in this process. An instruction is the basic unit of execution in a processor, and a thread is the object that carries out instructions. Every running process has at least one thread.

Working Set
Working Set is the current number of bytes in the Working Set of this process. The Working Set is the set of memory pages touched recently by the threads in the process. If free memory in the computer is above a threshold, pages are left in the Working Set of a process even if they are not in use. When free memory falls below a threshold, pages are trimmed from Working Sets. If they are needed, they will then be soft- faulted back into the Working Set before they leave main memory.

Virtual Bytes
Virtual Bytes is the current size in bytes of the virtual address space the process is using. Use of virtual address space does not necessarily imply corresponding use of either disk or main memory pages. Virtual space is however finite, and by using too much, the process may limit its ability to load libraries.

Private Bytes
Private Bytes is the current number of bytes this process has allocated that cannot be shared with other processes.

Pool Nonpaged Bytes
Pool Nonpaged Bytes is the size, in bytes, of the nonpaged pool, an area of system memory (physical memory used by the operating system) for objects that cannot be written to disk, but must remain in physical memory as long as they are allocated. Memory\\Pool Nonpaged Bytes is calculated differently than Process\\Pool Nonpaged Bytes, so it might not equal Process\\Pool Nonpaged Bytes\\_Total. This counter displays the last observed value only; it is not an average.

Pool Paged Bytes
Pool Paged Bytes is the size, in bytes, of the paged pool, an area of system memory (physical memory used by the operating system) for objects that can be written to disk when they are not being used. Memory\\Pool Paged Bytes is calculated differently than Process\\Pool Paged Bytes, so it might not equal Process\\Pool Paged Bytes\\_Total. This counter displays the last observed value only; it is not an average.