Operating System - HP-UX
1834941 Members
2130 Online
110071 Solutions
New Discussion

Re: application can't see all system memory

 
SOLVED
Go to solution
Poucet
Regular Advisor

application can't see all system memory

hi
I'm runing an HPOV NNM 7.51. The serveur is an HP-UX 11.23 itanium with 4 CPU's and 16Go RAM.
My first problem is that NNM can see only 4Go of memory instead of 16Go.

my second problem is that one of the processes application (ovet_poll), use more and more memory until 970Mo then crash. the error message is "out of memory". I have increse the "maxdsiz" kernel parameter to 2Go with no result.

any advice?
thanks
9 REPLIES 9
Peter Godron
Honored Contributor
Solution

Re: application can't see all system memory

Hi,
from another thread:
"If ovet_poll is the one consuming too much memory then you can use a parameter called "loadOnlyPolledObjectsIntoMemory" in paConfig.xml file. Turn it to true and the mem usage of ovet_poll should come down."
Dennis Handly
Acclaimed Contributor

Re: application can't see all system memory

>my second problem is that one of the processes application (ovet_poll), use more and more memory until 970Mo

You can't use more than 1 Mb, unless you link with -N. You could also try chatr +q3p enable.
And if you still need more: +q4p enable

The chatr trick won't work on IPF without linking with -N.
Laurent Menase
Honored Contributor

Re: application can't see all system memory

if your application is 64 bit you must also change maxdsiz_64bit which by default is 1G.

For the memory, do you see all the memory at boot time in the dmesg or in the messages displayed on the console?

check if some memory could not have been disabled
Poucet
Regular Advisor

Re: application can't see all system memory

thank for all your quick answers.
Gordon, the parameter "loadOnlyPolledObjectsIntoMemory" is already set to True.

Laurent, with vmstat i can see all of 16Go memory, i will check the "messages || dmesg" file any way. NNM is a 32bit application.

Denis, I'm sorry but i did understand what you mean, and what parameter to modify. can you please give me more details ?
regards
Hein van den Heuvel
Honored Contributor

Re: application can't see all system memory

>> Laurent, with vmstat i can see all of 16Go memory, i will check the "messages || dmesg" file any way. NNM is a 32bit application.


Those 16GB are physical, so pages where stuff can be put.
You probably have even more space, for that if you add the swap area.

However, a 32-bit has only 32 bit worth of address for a range of 2**32 = 4 Gigabyte (GB). A good chunk of that is reserved for system an libraries and shares, giving 'only' 1 GB of userspace by default.

As replied before, chatr can ofen be used to address a more than 1GB, but never more than 3GB , and some applications me have trouble when the addresses go above 1GB for the first time. (Those would be poorly written/broken applications, but still).

Please google, or check wikipedia form more info on virtual versus physical memory and address ranges.

Hope this helps,
Hein van den Heuvel

Laurent Menase
Honored Contributor

Re: application can't see all system memory

Hi Poucet,
when I talk about 64bits I was thinking about your ovet_poll, not nnm.

If your ovet_poll is a 32 bit application it is limited to 4 * 1Gb quadrant.
The data quadrant is only 1GB per process.
so you can play with exec_magic to go over that limit and use up to 2G or 3G of data memory.

There is some info at:
http://docs.hp.com/en/5187-0172/ch10s04.html
Poucet
Regular Advisor

Re: application can't see all system memory

thanks for all those clever answers
i will try all of this and let u know.
Dennis Handly
Acclaimed Contributor

Re: application can't see all system memory

>what parameter to modify. can you please give me more details?

If you don't own the product ovet_poll, you can't relink it with -N.

You would be able to change it to writable then use:
$ chatr +q3p enable ovet_poll
and get 2 Gb.
Steven E. Protter
Exalted Contributor

Re: application can't see all system memory

Shalom,

My first problem is that NNM can see only 4Go of memory instead of 16Go.


Do the file command on the binary and see whether it is 32 or 64 bit executable. If its 32 bit that will explain why it can't see more than 64 bits of memory.

32 bit apps that don't use memory windows are not going to see more than 2-4 GB of RAM no matter how you configure your system.

If you wrote the app, try for a 64 bit compile

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com