[Info-vax] Process memory settings

[Ken Fairfield]

On Aug 13, 9:05 am, "Syltrem" <syltremz... at videotron.ca> wrote:
[...]
>
> I lowered signifiicantly the PQL_MWSEXTENT and that of the user in UAF
> It induced a lot of page faults of course, and the Peak Virtual Size still
> grew to 847968, which is the same value I get to with higher settings of
> WSEXTENT.
> It always fails when it needs more memory than this, whether from the real
> memory of page file.
>
> WSMAX currently is set to 872448 which is close to this maximum Virtual Size
> I get. It looks like this is my upper boundary.
> PQL_MWSEXTENT normally is equal to WSMAX but I lowered it for this test.
>
> I think I'm going to install the cobol compiler on a test box that I can
> reboot, and play with WSMAX.
> It looks like it has an incidence not only on the working set, but on the
> total memory used by the process.

Due respect, I think you're missing the point.  While
WSEXTENT and WSMAX, etc., affect efficiency (by
reducing page faults), having them set too small will
*never* result in the "%LIB-F-INSVIRMEM, insufficient
virtual memory".  NEVER.

You're must be running into a combination of too small
PGFLQUO for the account, and/or the combination of
physical memory and page file space to support the
needed PGFLQUO (i.e., the needed virtual memory).

On the VAX there was a SYSGEN parameter that
also needed to be set, VIRTUALPAGCNT, IIRC.
But that parameter is obsolete on Alpha.  Again,
on the VAX, that would have needed to be set
less than the sum of physical memory plus
page file space...

    -Ken