Difference between revisions of "Talk:High Utilization"

From MicroFocusInternationalWiki
Jump to: navigation, search
(usage note)
 
(3 intermediate revisions by 2 users not shown)
Line 1: Line 1:
Hi,
+
=====
 +
Note that this page is for discussing editorial changes.  The abend-hangs forum is a
 +
good place to discuss actual utilization issues.
 +
=====
  
after the SP7 update on two NW6.5 Servers (from SP6) I've got high CPU utilization on one of the two processors on each server.
+
We'll follow along in the forums for now -- Massimo is tracking this, I think.
  
The output of the monitor.nlm:
+
/dps
  
    NetWare 6 Console Monitor  12.02.2                  NetWare Loadable Module
+
(That's re B Schilliger's Post-SP7 Java issue)
                           
+
    Product: Novell Open Enterprise Server, NetWare 6.5                         
+
  ¦+----------------------------------------------------------------------------+¦
+
  ¦¦              Busiest Threads and Interrupt on Processor 1                ¦¦
+
  ¦+----------------------------------------------------------------------------¦¦
+
  ¦¦  Processor 1: IDLE Thread                                        108'278  ¦¦
+
  ¦¦  Server 01:20                                                      11'427  ¦¦
+
  ¦¦  OS Allocated Timer Interrupt                                      4'436  ¦¦
+
  ¦¦  ACPIDRV.PSM Allocated Bus Interrupt                                1'634  ¦¦
+
  ¦¦  ACPIDRV.PSM Allocated Bus Interrupt                                  12  ¦¦
+
  ¦¦  Server 01:23                                                          0  ¦¦
+
  ¦¦  OS Allocated Bus Interrupt                                            0  ¦¦
+
  ¦¦  Server 01:15                                                          0  ¦¦
+
  ¦¦  Server 01:18                                                          0  ¦¦
+
  ¦¦  Server 01:19                                                          0  ¦¦
+
  ¦¦  Server 01:21                                                          0  ¦¦
+
  ¦¦  Server 01:22                                                          0  ¦¦
+
  ¦¦  Server 01:13                                                          0  ¦¦
+
  ¦¦  Server 01:24                                                          0  ¦¦
+
  ¦¦  Server 01:17                                                          0  ¦¦
+
  ¦¦  Server 01:26                                                          0  ¦¦
+
  ¦¦  Server 01:28                                                          0  ¦¦
+
  ¦+----------------------------------------------------------------------------+¦
+
  Esc=Previous list  F4=Previous Processor  F5=Next Processor          F8=More
+
  
Output of the NRM:
+
/dps
 
+
Execution Profile Data by Thread
+
Thread Name Thread ID Thread State Parent NLM Execution Time
+
Server 12 9066B3E0 Waiting for work SERVER.NLM 46.2 %
+
Java_408 Watcher 95688200 Yielded CPU JAVA.NLM 40.8 %
+
Server 01:20 894000E0 Waiting for work SERVER.NLM 9.1 %
+
ImgServ connect AC71D520 Blocked on a kernel CV IMGSERV.NLM 2.2 %
+
Processor 1: IDLE Thread 80942160 Ready to run / running SERVER.NLM 0.6 %
+
Health Monitor Slow 9355E420 Delayed PORTAL.NLM 0.2 %
+
Server 00:79 8A5A50C0 Waiting for work SERVER.NLM 0.1 %
+
 
+
Have you'got any ideas, what's the matter?
+
 
+
Thanks for help.
+
 
+
Regards from Switzerland
+
Beat
+

Latest revision as of 21:14, 30 November 2007

=

Note that this page is for discussing editorial changes. The abend-hangs forum is a good place to discuss actual utilization issues.

=

We'll follow along in the forums for now -- Massimo is tracking this, I think.

/dps

(That's re B Schilliger's Post-SP7 Java issue)

/dps