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

Conference bulova::decw_jan-89_to_nov-90

Title:	DECWINDOWS 26-JAN-89 to 29-NOV-90
Notice:	See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit
Moderator:	STAR::VATNE

Created:	Mon Oct 30 1989
Last Modified:	Mon Dec 31 1990
Last Successful Update:	Fri Jun 06 1997
Number of topics:	3726
Total number of notes:	19516

1291.0. "How is X$PUT_IMAGE Implemented ?" by CUJO::MEIER (Systems Engineering Resident...) Wed Aug 16 1989 19:12

    Would someone share with me the method of implementation choosen
    for X$Put_Image routine?
    
    		MY customer is attempting to update most of the
    		entire FIREFOX screen at near refresh rate.
    		However the amount of CPU time is near 80%
    		continuously.
    
    		Will DECW Version 2.0 reduce the amount of
    		CPU time required to support this operation?
    
    	Direct feedback is welcomed
    
    		(303) 341-3934....

T.R Title User Personal
Name Date Lines

1291.1 Hmmmmm.... GSRC::WEST Schizophrenia beats being alone. Fri Aug 18 1989 02:25 27

T.R	Title	User	Personal Name	Date	Lines
1291.1	Hmmmmm....	GSRC::WEST	Schizophrenia beats being alone.	`Fri Aug 18 1989 02:25`	27
	>> MY customer is attempting to update most of the >> entire FIREFOX screen at near refresh rate. >> However the amount of CPU time is near 80% >> continuously. Do you know if it was the server that was utilizing most/all of this time? >> Will DECW Version 2.0 reduce the amount of >> CPU time required to support this operation? Don't know. On the Firefox the Low End Graphic Sub-System (LEGSS) is controlled by a dedicated CVAX with a Wietek 3-chip set and pixel rendering chips (A,D,T). Pixel rendition is done at the rate of 100,000,000 pixels per second. This is all done with hardware. I am not exactly sure what all the server does with respect to a Firefox. The server code works directly with the hardware. I know that the server is responsible for the frame buffer memory management and that there are some problems in this area. However, I have been able to 'see' better response when the server's quotas have been upped. There are three logicals that can help. DECW$SERVER_WSEXENT, DECW$SERVER_WSDEF, DECW$SERVER_WSQUOTA. The file that uses them is SYS$MANAGER:DECW$STARTSERVER.COM. Give these a try and see if this help. -=> Jim <=-

    
>>    		MY customer is attempting to update most of the
>>    		entire FIREFOX screen at near refresh rate.
>>    		However the amount of CPU time is near 80%
>>    		continuously.

  Do you know if it was the server that was utilizing most/all of this time?
    
>>    		Will DECW Version 2.0 reduce the amount of
>>    		CPU time required to support this operation?

  Don't know.  On the Firefox the Low End Graphic Sub-System (LEGSS) is
  controlled by a dedicated CVAX with a Wietek 3-chip set and pixel rendering
  chips (A,D,T).  Pixel rendition is done at the rate of 100,000,000 pixels per
  second.  This is all done with hardware.  I am not exactly sure what all the
  server does with respect to a Firefox.  The server code works directly with
  the hardware.  I know that the server is responsible for the frame buffer
  memory management and that there are some problems in this area.  However,
  I have been able to 'see' better response when the server's quotas have been
  upped.  There are three logicals that can help.  DECW$SERVER_WSEXENT, 
  DECW$SERVER_WSDEF, DECW$SERVER_WSQUOTA.  The file that uses them is
  SYS$MANAGER:DECW$STARTSERVER.COM.  Give these a try and see if this help.

					-=> Jim <=-