Difference between revisions of "High Utilization"

From MicroFocusInternationalWiki
Jump to: navigation, search
 
m (corrected type)
Line 16: Line 16:
 
(a unit of processor execution) that is the cause of the high utilization.
 
(a unit of processor execution) that is the cause of the high utilization.
  
se Monitor.nlm (tab to "next window", then select Kernel->Busiest Threads) or  
+
Use Monitor.nlm (tab to "next window", then select Kernel->Busiest Threads) or  
 
NRM (Diagnose Server->Profile/Debug->Profile CPU Execution by NLM)  
 
NRM (Diagnose Server->Profile/Debug->Profile CPU Execution by NLM)  
 
to see what is listed.  
 
to see what is listed.  

Revision as of 04:20, 27 March 2007

Draft High Utilization Wiki

Starting point for wiki article on diagnosing high utilization

High Utilization is a popular topic in the support forums (novell.support.netware.6x.abends-hangs, for instance, and this forum is mirrored in novell.support.open-enterprise-server.netware.abend-hangs; see also novell.support.netware.6x.administration-tools/novell.support.open-enterprise-server.netware.administration-tools)

High utilization can keep a system administrator's phone or help desk busy, as users may experience delays in accessing files or print services or web pages.

Finding the Thread

Use the follwoing techniques to find the thread (a unit of processor execution) that is the cause of the high utilization.

Use Monitor.nlm (tab to "next window", then select Kernel->Busiest Threads) or NRM (Diagnose Server->Profile/Debug->Profile CPU Execution by NLM) to see what is listed. If you're uncertain about the meaning of what you see, paste the output from one these tools into a posting in the support forums.

Note that threads listed as "server 09" and such are generally handling NCP requests from clients, so if such a thread is busiest, then check your workstations.

Abend Hunting

High Utilization sometimes turns into an Abend. See the following article for more on diagnosing an Abend AbendHunting.

Room for Corrections

Looking forward to the sysops' notes on this page.