[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference csc32::consolemanager

Title:POLYCENTER Console Manager
Notice:Kits, Scans, Docs on CSC32:: as PCM$KITS:,PCM$DOCS:, PCM$SCANS:
Moderator:CSC32::BUTTERWORTH
Created:Thu Aug 06 1992
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1541
Total number of notes:6564

304.0. "C3 STATUS Panel Consumes CPU" by BSS::LIND (Jim Lind; 592-4099 CX03-1/N14 CNMC-West) Wed Jul 13 1994 21:26

    ISSUE:  System Status from C3 consumes CPU without update
    
    V1.5 of PCM; V6.1 of VMS
    
    In the C3 DISPLAY, I request a status panel:
    
    	Commands
    		System Status ...
    
    (1)  Under certain circumstances, the panel can be VERY slow in 
    		being created - reason/conditions unknown
    
    (2)  After the system status panel is created, CPU is consumed
    		while the panel is left on the screen.
    
    (3)  If the CONSOLE display is iconized (with the status window)
    		when the window is recalled, the STATUS panel can be
    		VERY slow in being re-painted (updated).
    
    On a 6340 running PCM, from 40-100% of one processor consumed 
    with the display.
    
    It is unclear why the CONSOLE STATUS is so much faster than the status
    panel in the C3 interface.
    
    The C3 System Status display is apparently dynamic, continually
    being updated.  However, this behavior is different from the 
    DCL interface, which is a one shot deal (not dynamic).  The
    documentation does NOT indicate the dynamic nature of the status panel,
    nor does it warn of the drain on CPU resources.
    
    I suggest engineering consider making the C3 status panel static - a
    one shot deal to display CURRENT status.
    
    Jim Lind
T.RTitleUserPersonal
Name		DateLines
304.5OPG::PHILIPAnd through the square window...Thu Jul 14 1994 10:4317
Jim,

  The DCL Status display is dynamic if you add the /CONTINUOUS
  qualifier to your command, you can also add /INTERVAL=num_seconds
  to have a faster update rate e.g.

$ CONSOLE STATUS/CONTINUOUS/INTERVAL=1

or on ULTRIX and OSF/1

# console -d -c -i 1

  As for the C3 bits, I leave that to Dave Bigelow as he wrote
  it all.

Cheers,
Phil
304.6perplexedZENDIA::DBIGELOWInnovate, Integrate, EvaporateThu Jul 14 1994 14:2415
    Jim,
    
    I just tried it on my VAXstation 3100 model 48 which is a very slow
    system compared to a 6340 and there is no noticable degradation in 
    performance. I issued a 'monitor system' command just to make sure
    and nothing stood out as being a CPU hog. I wonder if it has to do with
    the fact that you have SMP. During the C3 status interval, all it does 
    is to go to sleep, waitng for the operating system to deliver an interupt
    to wake up.
    
    Do you DECps installed. Id so, can you do a little poking around with
    it? I'd be more than happy to fix this if I know what the problem
    was/is.
    
    Dave
304.7CSC32::BUTTERWORTHGun Control is a steady hand.Thu Jul 14 1994 18:0812
    Something has happened to the other replies in this note...... Phil
    I have had this happen to another notesfile that I moderate and I had
    to reorganize the file as I had some corrupt buckets.
    
    I also tried to reproduce this on a 4000/60 and cannot. The top cpu
    consuming process was only 7% and was not the C3. Lot's of idle time
    left-over too.
    
    Dan
304.8OPG::PHILIPAnd through the square window...Thu Jul 14 1994 18:109
Dan,

  This notesfile is OK, what happened was we ran out of disk
  space last night, the disk this notes conference is on just
  happens to be the disk I was using to test the new daemon
  I have been working on.

Cheers,
Phil