🚀 go-pugleaf

In article <261500008@S34.Prime.COM>, BEAR@S34.Prime.COM writes:
>     I believe what you're looking for is a working set scheduler. In a
> nutshell, this type of scheduler pages a job against itself rather than
> against the system (i.e. the pool of available pages belongs to the process
> (rather than the system) and is of a size set by the system when then process
> is created). Unfortunately, I can't think of an available OS that uses a WS
> scheduler off the top of my head (that doesn't mean they don't exist!). Good
> luck.

I must be lucky then.  VMS has had one since day one.  Working set 
parameters can be set by either authorization information, as parameters 
to the $CREPRC system service (which creates a process) or explicitly 
during process execution (SET WORKING_SET command, or $ADJWSL system 
service).  Their are three parameters - default working set, working set 
quota (amount of WS that a process can "expect" to have when running) and 
working set extent (maximum WS that a process can get at if there is free 
memory on the system).  There are current and authorized values for these 
parameters.  I tend to run processes with lowish WSdefault and WSquota, 
and a high WSextent - means that processes that need memory can get it if 
it is available, but don't hog memory.

Don Stokes, Systems Programmer    /  /   Domain:                  don@gp.govt.nz
Government Printing Office,      /GP/   PSImail:          PSI%0530147000028::DON
Wellington, New Zealand         /  /   Bang:    ...!uunet!vuwcomp!windy!gpwd!don
--------------------------------------------------------------------------------
A shortcut is the longest distance between two points.