- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Command line memory monitoring
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
Forums
Discussions
Discussions
Discussions
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
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
03-01-2006 10:01 PM
03-01-2006 10:01 PM
I think this subject was probably discussed many times, but I could not find any answer - even on this forum - that completely helped.
I'd like to get regular memory stats and store them in a basic text file, in order to process them later with a perl script.
Information I look for is :
- buffer cache size
- pages number that are used (minus the buffer cache)
- pages number that are page out or swapped out
To sum up, I'd like to know easily if my system is under memory pressure or not, nothing really special... :)
It doesn't seem to me that vmstat provide all this information, and I know I could use glance but it doesn't fit my needs (maybe I'm wrong, I'm quite new in HP-UX administration).
HP-UX virtual memory implementation is rather complex, and I feel like each memory monitoring tool provide a part of what I'd like to know.
Can anyone give me some clue about the way to handle this ?
Sorry - again - for my approximative english.
Yann
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-01-2006 10:16 PM
03-01-2006 10:16 PM
Re: Command line memory monitoring
I run a script that extract data in a xls file, then I ftp the files to a windows machine where I plot the datas with excel.
You can look at the link below where I posted the extract command and a configuration file aimed to gather memory and swap info, but I suggest you to go deeper in the reptfile metrics you can use.
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1006074
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-01-2006 11:33 PM
03-01-2006 11:33 PM
Re: Command line memory monitoring
The simplest metric is vmstat -s in conjunction with vmstat -z. vmstat -s gives you a list of 1-liners (vmstat without options is a pain to script), but the most important "memory pressure" metric is page out (use grep to isolate that line from vmstat -s). This is the number of pages that were forced out to the swap area because there is no room in RAM. Single digits (0-9) are normal and of no concern, 2 digits (10-99) is an indication that RAM is short, and 3 digits or more indicates severe memory shortage.
Now it is normal for short bursts of page-outs to occur, especially in an interactive system (where users think for a while between transactions). Use the vmstat -z option to clear the counters so the values are meaningful over a short measurement period, like 5 mins. Page in is not meaningful because HP-UX starts all programs by paging in the various parts of the program from it's executable file, as well as paging in a program which was previously paged out to the swap area. This one metric is the best indicator of memory pressure since it has a huge impact on overall system performance.
Bill Hassell, sysadmin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-02-2006 01:37 AM
03-02-2006 01:37 AM
Re: Command line memory monitoring
It doesn't seem like extract is designed to provide regular "samples" of system memory, am I wrong about this ?
Otherwise I didn't know about these vmstat options. I think they're going to be useful in my case. Sorry to be so picky but can I combine vmstat with something else so that I can get a general idea of memory usage --> the purpose is to generate some graphs, and I wouldn't have so many things to graph if the server doesn't page out...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-02-2006 02:45 AM
03-02-2006 02:45 AM
Re: Command line memory monitoring
You could create an application group for your procs and tune the logging thereshold value in the same file.
Have a look at:
/opt/perf/examples/mwaconfig/parm_apps
/var/opt/perf/parm #here the config to create groups and tune thereshold
man mwa
man midaemon
Regards.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-02-2006 04:04 AM
03-02-2006 04:04 AM
Re: Command line memory monitoring
Now I'm more familiar with the mwa operation, ant outputs provided is indeed just what I need. However, I've read both /opt/perf/examples/mwaconfig/parm_apps and /var/opt/perf/parm very carefully and I didn't find out how to change the measures rate.
I did a quick export test about CPU load and got this ouptut :
Date |Time |CPU % |
03/02/06|00:00| 8.33|
03/02/06|00:05| 14.35|
...
Is the CPU load an average value for a 5 minutes interval, or is it an instantaneous value --> couldn't find information in man pages or file comments. In this case I'd like to turn down the test rate to 1 minute.
Thanks again, I really appreciate the support.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-02-2006 04:40 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-02-2006 09:26 AM
03-02-2006 09:26 AM
Re: Command line memory monitoring
I didn't know mwa at all. I going to dig a little deeper... :)