OpenVMS 7.3-2, too process in Swapped Out state

[rison so_1]

Just upgrade to OpenVMS7.3-2 and found a lot of process in "Swapped Out" State. Attached the output from "show memory" and "show system"

[Thomas Ritter · Accepted solution]

Bit short on memory ?

Physical Memory Usage (pages): Total Free In Use Modified
Main Memory (2.00GB) 262144 5965 247692 8487

What version did you upgrade from ?

[Volker Halle]

Your system is apparently a little 'short on memory' and OpenVMS has swapped out (inactive) processes to regain memory.

This is not a problem, if those processes remain inactive for an extended period of time. You can use MONITOR IO to see, if there is a significant Inswap rate, this would be a reason for concern.

Volker.

[Volker Halle]

Do you have a SHOW SYSTEM or SHOW MEMORY output from before the OpenVMS upgrade ?

There are lots of SRVnn_NAVIGATO processes, is that a normal load for your system ?

Volker.

[rison so_1]

It was upgraded from V7.3-1 to V7.3-2.
But we didn't have this problem before the upgrade.

[Thomas Ritter]

Rison, you clearly have a memory shortage. Check the number of process which were run before the upgrade.
62% of your processes are outswapped.

What are the 270 SRV223_NAVIGATO processes ?

[Volker Halle]

The 264 SRVnn_NAVIGATO processes seem to consume up to 214171 Alpha pages, this would be 1.7 GB out of your total of 2 GB of physical memory.

Find out using F$GETJPI(pid,"PPGCNT") and F$GETJPI(pid,"GPGCNT") how much pages in the working of those processes are global or private.

Maybe something isn't installed /SHARED ?

Volker.

[rison so_1]

I did increase the MAXPROCESSCNT from 600 to 1000 after the upgrade.

Those are Attunity connect process, SEVnn_Navigator.

[Wim Van den Wyngaert]

You have about 650 processes active.
Your old maxproc was at 600. So, this is NOT the same load. So it could be normal.

Wim

[Wim Van den Wyngaert]

BTW : release notes 7.3-2

The Attunity Connect "On Platform" Package, part of the OpenVMS e-Business
Infrastructure CD-ROM, will not be supported after May 31, 2004.

Wim

[Wim Van den Wyngaert]

Try diff sys$system:setparams.dat ;-3
(replace ;-3 with the version that was 7.3-1.

May be important parameters were changed during the upgrade (e.g. wsmax). Post the result of diff.

Wim

[rison so_1]

SETPARAMS.DAT;41 is from the 10/JUL/06 and SETPARAMS.DAT;13 is from the 11/MAY/06.

Upgrade was done on the 10/JUN/06

[Wim Van den Wyngaert]

I only see minor differences that can't explain the swapped out unless your system was already "full as an egg" (btw : you maxproc was at 732, not 600).

But as long as you don't have performance problems, nothing is wrong. If the inswap delays the users, you can decrease the wsquota parameter of the users using navigator (e.g. by 10%). Of course you need to restart the sessions after that.

Wim

[rison so_1]

Thanks all for your help.

[rison so_1]

.

[Wim Van den Wyngaert]

I assume you did an autogen and did a diff to see what VMS proposes as changes to the parameters ?

Wim

[rison so_1]

Yes, I did the change according to Autogen report.

[Robert Gezelter]

Rison So,

Please take note of the comment that Volker made about the images being installed SHARED.

The INSTALL LIST command will produce a list of all installed images. If the image being used by a large number of your processes is not installed, you will be using large amounts of memory to hold identical, read-only pages.

Thus, using INSTALL to install shareable images, you may be able to reduce the amount of memory used by several orders of magnitude (factor of 1,000 to 10,1000).

- Bob Gezelter, http://www.rlgsc.com