HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- max use unshared memory for a process
Operating System - HP-UX
1835691
Members
2441
Online
110082
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- 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
08-20-2002 02:19 AM
08-20-2002 02:19 AM
How can I detect how much unshared memory can be used at most by 1 process ?
This will definitely be equal to the memory size minus the shared memory, but I would like to know if there are other limits.
HP-UX 11
Thanks in advance
Franky Leeuwerck
This will definitely be equal to the memory size minus the shared memory, but I would like to know if there are other limits.
HP-UX 11
Thanks in advance
Franky Leeuwerck
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-20-2002 02:35 AM
08-20-2002 02:35 AM
Re: max use unshared memory for a process
buffer cache:
dbc_max_pct
dbc_min_pct
And about forty other kernel parameters that consume memory.
When in doubt add more memory and use the new memory for your process.
live free or die
harry
dbc_max_pct
dbc_min_pct
And about forty other kernel parameters that consume memory.
When in doubt add more memory and use the new memory for your process.
live free or die
harry
Live Free or Die
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-20-2002 02:47 AM
08-20-2002 02:47 AM
Solution
Try this document:
http://www.faqs.org/faqs/hp/hpux-faq/section-140.html
or this:
http://www.interex.org/conference/iworks2001/proceedings/1034/1034.pdf
live free or die
harry
http://www.faqs.org/faqs/hp/hpux-faq/section-140.html
or this:
http://www.interex.org/conference/iworks2001/proceedings/1034/1034.pdf
live free or die
harry
Live Free or Die
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-21-2002 08:07 AM
08-21-2002 08:07 AM
Re: max use unshared memory for a process
There are many different limits on memory use, so it is complicated to find out which limit a process will reach first. Here is a list-
- All processes are limited by the available swap, which can be checked with "swapinfo -t" or pstat_getswap(). The value will change as other programs use more or less swap. You can cheat a little on swap allocation by using "chatr +z", but you risk an unexpected exit.
- All processes are limited by the ulimit values that you can check with the shell ulimit commands or getrlimit().
- Processes are limited by the kernel maxdsiz or maxdsize_64bit parameters.
- 32-bit processes are limited by the address space. Processes linked with '-N' start mallocing at the top of the text and data areas. Processes linked without '-N' start mallocing around 0x40000000. Their malloc calls are then stopped at 0x80000000 unless the ld/chatr +q3p feature is used to allow them to grow to almost 0xc0000000. The 11i release also has a +q4p feature that allows malloc to reach almost 0xf0000000.
I have attached a couple of programs that report some memory features affecting maximum data size.
- All processes are limited by the available swap, which can be checked with "swapinfo -t" or pstat_getswap(). The value will change as other programs use more or less swap. You can cheat a little on swap allocation by using "chatr +z", but you risk an unexpected exit.
- All processes are limited by the ulimit values that you can check with the shell ulimit commands or getrlimit().
- Processes are limited by the kernel maxdsiz or maxdsize_64bit parameters.
- 32-bit processes are limited by the address space. Processes linked with '-N' start mallocing at the top of the text and data areas. Processes linked without '-N' start mallocing around 0x40000000. Their malloc calls are then stopped at 0x80000000 unless the ld/chatr +q3p feature is used to allow them to grow to almost 0xc0000000. The 11i release also has a +q4p feature that allows malloc to reach almost 0xf0000000.
I have attached a couple of programs that report some memory features affecting maximum data size.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP