- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: memory management
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
тАО06-07-2001 05:54 PM
тАО06-07-2001 05:54 PM
memory management
Here is J5000 [10.20] with 3G memory installed. It is runing mathematical simulator/solver.
---------------------------------------------------
# dmesg | grep Physical
Physical: 3145728 Kbytes, lockable: 2310124 Kbytes, available: 2651032 Kbytes
# top
...
Memory: 910748K (899208K) real, 959264K (946304K) virtual, 1161884K free Page# 1/5
CPU TTY PID USERNAME PRI NI SIZE RES STATE TIME %WCPU %CPU COMMAND
1 pty/ttyp2 19244 user 255 39 925M 872M run 500:22 100.04 99.86 dessis
...
---------------------------------------------------
Two questions:
1. Top show 967736K real + 1134056K free only.
Is there any way I can release more memory for process?
[strangely, glanceplus shows account for 3gb !!
Phy 3.0g Sys mem:307m, Buffer cache: 368m
User mem:1.23g, Free mem:1.1g ]
2. In the above top output, the resident size of "dessis" is 925M.
It can take more than that. It did so in other 11.0 machine.
What kernal parameter(s) do I need to tweak to allow a single
process consume more, if not "all" available, memory?
TIA.
-elan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-07-2001 06:16 PM
тАО06-07-2001 06:16 PM
Re: memory management
I've run similar applications and yes you need all the memory you can get.
You should increase maxdsiz, possibly maxssiz,
and sometimes maxtsiz needs to be increased as well. If the program will run, maxtsiz is probably big enough. You might also need to increase shmmax. I would also make sure that I have enough swap and/or enable pseudo-swap (swapmem_on=1). Typically, disk i/o is not all that important so I would reduce dbc_max_pct to no more than 10% or set bufpages to limit buffer cache to no more than 100MB. This program might also benefit from using "memory windows" since you are running 10.20. You can search this site for that concept.
Happy number crunching, Clay
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-07-2001 06:20 PM
тАО06-07-2001 06:20 PM
Re: memory management
From the Configurable Kernel Parameters (HP-UX 11.0) document:
http://docs.hp.com/hpux/onlinedocs/os/KCparams.OverviewAll.html
> The kernel parameters 'maxdsiz' and 'maxdsiz_64bit' specify the maximum data segment size, in bytes, for an executing process.
> 'maxssiz' and 'maxssiz_64bit' define, for 32-bit and 64-bit processors respectively, the maximum size of the dynamic storage segment (DSS), also called the user-stack segment, or an executing process's run-time stack. This segment contains stack and register storage space, and such.
> 'maxtsiz' and 'maxtsiz_64bit' define, for 32-bit and 64-bit processors respectively, the maximum size of the shared text segment (program storage space) of an executing process.
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-07-2001 06:29 PM
тАО06-07-2001 06:29 PM
Re: memory management
My current parameters are:
maxdsize 2063835136
maxssize 83570688
maxtsize 1073741824
dbc_max_pct 50
dbc_min_pct 5
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-08-2001 03:05 PM
тАО06-08-2001 03:05 PM
Re: memory management
maxdsize 2063835136
maxssize 401604608
maxtsize 1073741824
shmmax 2063835136
By reducing the percent of dynamic buffer (dbc_max_pct), now more memory is shown free. Yet the resident size of the process does not go beyond 974M as reported in top. While the same program takes more than 1.7 G on other 11.x machine.
Any clue about grabbing all the memory for this process?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-09-2001 07:18 PM
тАО06-09-2001 07:18 PM
Re: memory management
The maxdsiz value can be set much higher than the maximum usable value in a program as it is simply a fence to prevent problem prgrams from running wild. Thus, setting it to 2000 megs will have no effect (as you have seen).
However, you can link two quadrants together to allow up to 1750 megs for a 32-bit program. Look at the EXEC_MAGIC features mentioned in the memory managment while paper in /usr/share/doc. It's important to note that from a memory management point of view, 10.20 is very different from 11.0 64-bit. Note that the dynamic buffer cache should never be 50% max...perhaps 15-25% at most. But even at 50%, it will shrink automatically if processes need the space.
Bill Hassell, sysadmin