[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

2759.0. "server's working set not reduced after XUnloadFont" by TAV02::GAN () Tue May 15 1990 10:13

One of our customers is writing XLIB (VMS 5.2) application
which loads 6 fonts when it starts. Just before it ends,
he uses X$UNLOAD_FONT to unload all 6 fonts. since this
is the only application running, he assumes that DECW$SERVER_0
working set should decrease it's size approximately by these
fonts size (1500 pages). But it don't. The server's working
set remains as it was before the unload. The only way to
reduce it's working set is to initialize the server by quitting
the session.

In the XLIB manual it states that X$UNLOAD_FONT should close
the file and remove from memory if no other client uses these
fonts. Does it means also working set size reduce for the
server? He want to reduce it's working set to avoid page faults
and/or swapping.

		Ofer Gan

T.R Title User Personal
Name Date Lines

2759.1 DECWIN::FISHER Prune Juice: A Warrior's Drink! Tue May 15 1990 14:19 15

T.R	Title	User	Personal Name	Date	Lines
2759.1		DECWIN::FISHER	Prune Juice: A Warrior's Drink!	`Tue May 15 1990 14:19`	15
	Are we using the same definition of working set? Reducing the working set typically results in MORE page faults. The WS is essentially the amount of virtual memory that a process is allowed to have mapped to real memory at any one time. If you need memory outside your working set, that generates a page fault. In any case, whether you are talking about working set or virtual page count, memory never gets completely returned. It is either cached away in the server or in LIB$GET_VM and reused the next time it is requested. You will never see the virtual page count go down in any process (till the image exits). The working set size may correspond over time to the amount of memory in active use (more page faults tends to keep the working set high), but you won't see it drop immediately. Burns

Are we using the same definition of working set?  Reducing the working set
typically results in MORE page faults.  The WS is essentially the amount of
virtual memory that a process is allowed to have mapped to real memory at any
one time.  If you need memory outside your working set, that generates a page
fault.

In any case, whether you are talking about working set or virtual page count,
memory never gets completely returned.  It is either cached away in the server
or in LIB$GET_VM and reused the next time it is requested.  You will never see
the virtual page count go down in any process (till the image exits).  The
working set size may correspond over time to the amount of memory in active
use (more page faults tends to keep the working set high), but you won't see
it drop immediately.

Burns