13
« on: June 08, 2025, 12:10:12 am »
I really don't think the Available virtual memory is accurate as it seems to bounce all over the place. Here with Dooble and SM running, I get close to the same value as Neil.
Total physical memory: 16,270 MB
Accessible to system: 3,502 MB
Additional (PAE) memory: 12,768 MB
Resident memory: 180 MB
Available virtual memory: 1,443 MB
Available process memory:
Private low memory: 306 MB
Private high memory: 1,956 MB
Shared low memory: 220 MB
Shared high memory: 99 MB
I would suggest having a much larger starting value for the swap file to avoid the overhead of growing it, perhaps 1.5 GB and also keep an eye on it. Back in the day I had a system with 1.5GB's of ram, linking xul.dll needed VIRTUALADDRESSLIMIT=3072 or wlink would run out of memory. I had to be careful not to overflow the swap file as the system would die with a swap file full error once the swap file grew to about 2GB. It was on JFS but I assume internally OS/2 uses signed 32 bit variables. I'm sure back in the early 90's it was never expected to use so much memory and/or swap.