Dear Managers,
Sorry about the delay in posting this summary.
Thanks to the following who provided me with some insight into virtual 
memory.
N.M.Hill_at_rl.ac.uk
juredd_at_axcion.com
Caprica7_at_aol.com
Firstly, the amount of virtual memory has nothing to do with physical 
memory.  I do remember from my DU training courses that there is not 
enough memory in the world that DU can address.
The nub of the replies was that you can increase the amount of virtual 
memory that a user can use by adjusting the following.
vm:
 vm-maxvas
proc:
 per-proc-data-size
 max-per-proc-data-size
 max-per-proc-address-space
 per-proc-address-space
These parameters were increase to 2147483648 each, apart from 
per-proc-data-size which was set to 262144000.  The system was rebooted 
and each users vmemory value (from ulimit -a) indicated an increase 
from 1Gb (the default) to 2Gb.
One gotcha is that ulimit displays different things depending which 
shell you use, the 3rd party support company was using csh which  
increased values considerably.
It got to the stage where the 3rd party came onto site to perform a 
health check of the application and OS.  It turned out that ingres 
required tuning and the number of threads it used increased.
Nice to know that ingres can have a bad day too.
Simon
Simon.Millard_at_barclays.co.uk
Group Mail: Simon S.G. Millard
Address                                  Telephone
SD&D - GES/Open Systems Support       External: (01202) 601155 ext 2417
Barclays Technology Services                 Internal: C/W 7-4160-2417
Poole Computer Centre                            Fax: (01202) 642429
81, Sopers Lane                                 
Poole, Dorset                                      
"When I feel depressed I sit under a willow tree by a cool river and 
imagine that I am strangling a duck."
 - Kotaro Sarai
Disclaimer
========
Any views in this e-mail represent my personal views and not that of 
Barclays Bank PLC
Internet communications are not secure and therefore the Barclays Group does
not accept legal responsibility for the contents of this message. Any views
or opinions presented are solely those of the author and do not necessarily
represent those of the Barclays Group.
Received on Mon Jul 19 1999 - 07:54:57 NZST