On Tue, 26 Jan 1993 18:29:32 +0100 Eric Thomas said:
>I have just noticed that many LISTSERV functions will perform much better
>if you add SET RELPAGE OFF to LISTSERV's profile. For instance, a refresh
>of the LISTS database takes 24.8 seconds of VCPU on SEARN with the normal
>RELPAGE ON setting and 19.8 (20% off) with RELPAGE OFF. The only drawback
>is that, if LISTSERV needs a lot of storage to perform a certain function
>and then  releases it,  it will not  notify CP that  the contents  of the
>pages are no longer important. This forces  CP to keep page slots on DASD
>for the  corresponding virtual memory  locations, and it may  take longer
>for the real memory frames to be reallocated to another user since CP has
>to assume  they are still needed  until they have been  unreferenced long
>enough. The paging DASD allocation issue is negligible on anything bigger
>than a  9370 with 5  users whereas the  recycling time problem  will only
>impact small to medium page-bound systems  (on a large system LISTSERV is
>just a  user among a thousand  and it doesn't make  any difference). This
>command will be included in the startup code in the next release.
 
This is a know problem, and has been fixed in VM/ESA R2 with the pending
page release enhancements.  So you'll probably want to make the command
conditional on the release of CP & CMS.
 
Brent Stilley,  Oklahoma State University, 113 Math Sciences, Stillwater, 74078