Index on Network Address Causes High Utilization

  • 3040744
  • 06-Feb-2007
  • 26-Apr-2012


Novell eDirectory 8.7.3 for Linux
Novell eDirectory 8.7.3 for Solaris
Novell eDirectory 8.7.3 for NetWare 6.5
Novell eDirectory 8.7.3 for Windows 2000/2003


eDirectory can go into high utilization if an index is on the Network Address attribute.
Write locks can be excessive. In this example the Sched Delay Max is longer should not be over 1000000.

Threads: Thread Pool Information
Summary : Spawned 78, Died 0
Pool Workers : Idle 19, Total 78, Peak 78
Ready Work : Current 0, Peak 4, maxWait 11992 us
Sched delay : Min 11 us, Max 1000107 us, Avg: 4279 us
Waiting Work : Current 14, Peak 20"

You can check this information by doing an "ndstrace -c threads" from the linux commandline.

Another option to check if some threads are being delayed due to excessive time spent on Write Locks, is thru iMonitor. Open iMonitor on the suspect server, go to Agent Activity and in the first section, called DIB Writer Info, there will be a list of running processes. If these processes remain in the screen for a few seconds (remains between successive refreshes of the screen) or if the number displayed in the Time|Lock is one thousand or more, then there is a problem.


Remove index from Network Address.

This attribute is treated as a special case and should not be indexed. Specially when there are high values associated with it. If there is a specific need to index this attribute please contact Novell Technical Support.