- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- Re: memory allocation for programs
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-19-2005 08:22 AM
тАО01-19-2005 08:22 AM
amount of memory to set aside for each program a user runs in his
environment. That is when a user types in a programs name at the prompt
and hits "Enter" How does the loader figure out how much memory to set
aside for it to run. I think it needs some for code, some for stack
space, and some for data.
We have identical programs, running on different servers, that are
grabbing two different amounts of memory when they are run.
The two different servers are as follows -
1. Alpha 4100 running V4.0F PK7 - has 3GB RAM
2. Alpha ES40 running V5.1b PK4 - has 8GB RAM
On the ES40 the program grabs 10x the amount of memory that it does on
the 4100.
Tom Wallin
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-19-2005 01:34 PM
тАО01-19-2005 01:34 PM
Re: memory allocation for programs
ps -o RSS,VSZ ?
RSS is Real memory (resident set)
VSZ is Process virtual address size ... the program may or might not touch that all.
I suspect that RSS is similar, VSZ different.
I would also compare output for sysconfig -q proc
And check: ulimit -a
Hope this help some,
Hein.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-19-2005 05:17 PM
тАО01-19-2005 05:17 PM
Re: memory allocation for programs
can you post output of "ulimit -a" on both machines
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-19-2005 08:23 PM
тАО01-19-2005 08:23 PM
Re: memory allocation for programs
the two machines have a substantial difference in built in memory. There is a parameter that tells tru unix how much of a programme to hold in memory. With almost three times the memory size the es40 can hold more in memory.
greetings,
Michael
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-20-2005 01:46 AM
тАО01-20-2005 01:46 AM
Re: memory allocation for programs
Regards,
Tom Wallin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-20-2005 02:03 AM
тАО01-20-2005 02:03 AM
Re: memory allocation for programs
Your STACK size seems unreasonable:
ES40 ulimit -a
:
stack(kbytes) 4,194,304
That's 4 GB of stack, where you used 2MB before. The app worked with the 2MB right? So it shoudl still work with that.
4GB of stack is a whole bunch of pagetable pages also!
If you do not have a very good reason for to have set it that high, then just fix the sysconfig proc entry for the stack and be happy.
Hein.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-20-2005 02:13 AM
тАО01-20-2005 02:13 AM
Re: memory allocation for programs
Tom Wallin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-20-2005 03:47 AM
тАО01-20-2005 03:47 AM
Re: memory allocation for programs
a) Because I am in a BEA training with limited downtime :-).
b) Because that value is so clearly wrong (assuming you had a working system).
Typical sizes are 32M or so. If you need more (lots of local variables) then you wouls probably know.
c) I could imagine stack being different, as pages on either end will actually be touched.
'data' is just a fence. Just telling the system how far it can go, but you probably will not go there, so it does not matter if it is too far. However... if an application loses control, then it will not be stopped by this clean fence, but by some nasty resource depletion which my hurt other applications.
>> also does the loader use these values to calculate how much memory to set aside when loaded into memory.
Yes... but that is all 'virtual'. Just address ranges.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-20-2005 03:56 AM
тАО01-20-2005 03:56 AM
Re: memory allocation for programs
The ulimit list of stack size did not change either.
What kernel variable should I be changing?
Tom Wallin
ps Thanks for your time.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-20-2005 03:58 AM
тАО01-20-2005 03:58 AM
Re: memory allocation for programs
could you post the output of the ps as Hein first suggested from both machines?
thanks,
Michael