Conference wrksys::mikasa

892.0. "Dir/full eats Cpu time" by PRSSOS::AMAURY (Karl policy et lise plan) Mon May 05 1997 12:24

    
	Why my Dir/full command eats so much CPU time ?


	First step my customer receive a Alpha server 1000A 5/300
with the built in graphic device and VRC15 as screen 
	Customer start his session , opens a decterm , and
runs a directory command . 
------->in this state the DIR/full command eats 100% cpu time , 
all the cpu time for a single command !!!!!


	We said  the customer to change the card to speed up (because
the built in card is very  poor .... )

	Second step we installed a S3 trio 64 PCI 1Mb graphic accelerator
(PB2GA-JB) with the same performance       
(card set slot #3 in the primary bus)

	And third we swapped with the PCI 9FX Motion 331 (revision A01)
-------> but the same DIR/full command eats 80% CPU time (not really
satisfying !!!!!)


	I don't have a such configuration. 
	If someone is using a such configuration , could you test this
"slow" command on your system !

	Can someone explain why this command is consuming so much CPU ?


More information 

 OPENVMS V6.2-1H3
 DECWINDOW motif 1.2.4
 SYS$GQSdriver.exe  (22-Feb-1996)
 Alpha 1000A 5/300 srm 4.7-169
 Configuration with ECU 1.9
 Jumper J27 on mother board disabled 
 VRC15 set to 1024*768 70 hz supported
 Resoltuion defines in sys$manager:decw$private_server_setup.com
	$ DECW$XSIZE_IN_PIXELS ==1024
	$ DECW$YSIZE_IN_PIXELS == 768
	$ DEFINE/SYSTEM DECW$SERVER_REFRESH_RATE 70
 W've connected a VT320 on the serial port (on the server) 
and no excessive CPU time in this case 


	Thanks for your help 
	    - Michel -

Cross posted Mikasa and Decwindow conference.
    	

    
    	I bet a Jump Self would eat up close to 100% of the cpu and all for
    just one little program.
    
    	But you might want to look at some of the reasons DECterm may not
    perform up to expectations.
    
    	See HUMANE::DECTERM Topic 1593.5 and 1593.10
    
    						Bill