- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- Re: system performance.
Operating System - Tru64 Unix
1752826
Members
4343
Online
108789
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
Discussions
Discussions
Forums
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
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
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
тАО03-24-2005 08:07 PM
тАО03-24-2005 08:07 PM
system performance.
platform: V5.1A+PK6
1: how to identify the reason of IOwait is very high, the IOwait > 30
2: the output of vmstat -w 3
display fault cow pin very high, and I hope to find the root cause of this.
> vmstat -w 3 7
Virtual Memory Statistics: (pagesize = 8192)
procs memory pages intr cpu
r w u act free wire fault cow pin pout in sy cs us sy id iowait
18 478 154 350K 297K 120K 13G 1G 3G 0 6K 12K 14K 27 31 37 12
19 475 150 351K 296K 120K 13974 1336 2772 0 6K 87K 10K 50 50 0 30
21 474 149 352K 296K 120K 13190 721 1528 0 7K 112K 11K 51 48 0 34
16 474 151 350K 298K 120K 11560 798 2159 0 4K 113K 9K 55 45 0 21
13 477 153 352K 295K 120K 13728 891 2071 0 7K 121K 12K 53 47 0 9
17 474 149 350K 297K 120K 10470 696 1680 0 7K 100K 12K 58 42 0 16
16 474 150 352K 295K 120K 12065 750 1936 0 4K 116K 10K 62 38 0 5
Thanks
Jack
1: how to identify the reason of IOwait is very high, the IOwait > 30
2: the output of vmstat -w 3
display fault cow pin very high, and I hope to find the root cause of this.
> vmstat -w 3 7
Virtual Memory Statistics: (pagesize = 8192)
procs memory pages intr cpu
r w u act free wire fault cow pin pout in sy cs us sy id iowait
18 478 154 350K 297K 120K 13G 1G 3G 0 6K 12K 14K 27 31 37 12
19 475 150 351K 296K 120K 13974 1336 2772 0 6K 87K 10K 50 50 0 30
21 474 149 352K 296K 120K 13190 721 1528 0 7K 112K 11K 51 48 0 34
16 474 151 350K 298K 120K 11560 798 2159 0 4K 113K 9K 55 45 0 21
13 477 153 352K 295K 120K 13728 891 2071 0 7K 121K 12K 53 47 0 9
17 474 149 350K 297K 120K 10470 696 1680 0 7K 100K 12K 58 42 0 16
16 474 150 352K 295K 120K 12065 750 1936 0 4K 116K 10K 62 38 0 5
Thanks
Jack
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-25-2005 02:50 AM
тАО03-25-2005 02:50 AM
Re: system performance.
Interesting.
First of all, what makes you believe the IOwait is bad.
By explaining that we may be able to help you better.
I am not saying it is good, but it may be 'par for the course'.
For example. If the application mostly does random reads over a large (many GB) database, then IO wait is what you expect and what you will get. Nothing wrong with that.
Ditto for the 'cow'. If your application is constantly forking, then the cow is the natural and expected way to fill the address space for the data for the child.
The 'pin' rate would worry me most, but there again, with lots of forks, that would be the way to load the code pages for the children.
So what is your process creation rate?
What kind of box is this?(Wildfire?)
Roughly what is it supposed to be doing (Oracle?)
Did it ever work to your satisfaction? Is this new behaviour, or something that gradually went worse? Other then the vmstat observations, is there anything actually hurting?
I would start to run a quick kprof / dcpi / or trace or such tool to see what those 100K+ system calls / second are all about, and where all the system time is being burnt.
And I would run iostat (or monitor) to see which disks / domains the IOs are going to, at what rates/sizes.
Good luck!
Hein.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-27-2005 11:36 AM
тАО03-27-2005 11:36 AM
Re: system performance.
got it, Thanks
Jack
Jack
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP