- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: maxdsize_64_bit value?
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
тАО12-22-2003 06:40 AM
тАО12-22-2003 06:40 AM
Its current setting on an N4000 4-cpu 4GB ram system is 589824.
Was this an increase or decrease in its value?
It seems that some of our kernel settings got changed when some patches were installed on ISS. Is ISS known for doing this? The patches for it seem to have changed our kernel drastically, eg. dbc_max_pct went from 5 to 50!
Mott Given
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-22-2003 06:42 AM
тАО12-22-2003 06:42 AM
Re: maxdsize_64_bit value?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-22-2003 06:43 AM
тАО12-22-2003 06:43 AM
Re: maxdsize_64_bit value?
will give you value in decimal.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-22-2003 06:44 AM
тАО12-22-2003 06:44 AM
Re: maxdsize_64_bit value?
bc
ibase=16
90000000
That will then output the decimal (default output base or obase) with the input base (ibase) set to 16.
When finished, enter "quit".
Man bc for details.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-22-2003 11:15 AM
тАО12-22-2003 11:15 AM
SolutionNow as far as the dbc_max_pct value this is defaulted at 50. It seems the patch you loaded set it back to default. This is one of my biggest pet peeves about HP-UX. I learned in a performance tuning class that you can set the bufpages value and this will override your max/min_dbc_pct values to a static size. Off the top of my head the instructor stated that you really dont need more then 400-500MB for FS buffer cache. Obviously you would want to give this some thought if your system is mostly a fileserver. But if you run Sybase (or other RAW devices driven app) you may not need as much. But I feel that on most larger memory systems 50% is too much.
Hope this helps a little...
Alex
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-22-2003 02:09 PM
тАО12-22-2003 02:09 PM
Re: maxdsize_64_bit value?
http://docs.hp.com/cgi-bin/otsearch/getfile?id=/hpux/onlinedocs/939/KCParms/KCparam.MaxDsiz.html&searchterms=maxdsiz_64bit&queryid=20031222-195839
DESCRIPTION
User programs on HP-UX systems are composed of five discrete segments of virtual memory: text (or code), data, stack, shared, and I/O. Each segment occupies an architecturally defined range of the virtual address space that sets the upper limit to their size, but text, data and stack segments may have smaller maxima enforced by the maxtsiz, maxdsiz, and maxssiz tunables.
This tunable defines the maximum size of the static data storage segment for 32-bit and 64-bit processes. The data storage segment contains fixed data storage such as globals, arrays, static variables, local variables in main(), strings, and space allocated using sbrk() and malloc(). In addition, any files memory mapped as private and shared library per-invocation data also resides in the data segment.
When Should the Value of This Tunable Be Raised?
This tunable should be raised if user processes are receiving the ENOMEM error message:
exec(2): data exceeds maxdsiz
exec(2): data exceeds maxdsiz_64bit.
This may or may not cause a process failure depending on the program code.
What Are the Side Effects of Raising the Value?
Raising this tunable by definition allows larger data segments for every process. The maxdsiz and maxssiz tunables limit the amount of swap space that can be reserved or used by each process, but using more virtual address space does not translate directly into using more physical address space because virtual pages can be swapped out.
Note that if swap space on the machine is near capacity, raising this tunable increases the amount of reservable swap per process. This could exhaust the swap space on the system by allowing a process with a memory leak or a malicious program that uses huge amounts of memory to reserve too much swap space...
Please take the time to review some could technical docs on http://docs.hp.com/
for the dbc_max_pct, the best metrix is to run :
# sar -b 5 100
ideally you should see that %wcache is 95% or greater that means system is set in an optimal fashion. if the system shows consistently average(s) of 75% or lower you may consider lowering dbc_max_pct, check it out: http://docs.hp.com/hpux/onlinedocs/939/KCParms/KCparam.DBCmaxPct.html
Regards,
T+