- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- Re: Collect I/O stats report
Operating System - Tru64 Unix
1748014
Members
4151
Online
108757
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
тАО09-13-2005 02:09 AM
тАО09-13-2005 02:09 AM
Re: Collect I/O stats report
I am the original author of collect. I haven't maintained it for years, but I still know something about the data-collection landscape at digi.., uh, compa, uh, HP. Collect isn't always correct, because it's situated directly on top of kernel data-structures, and they have a nasty habit of changing from release to release. However, mostly, collect is correct, and if collect can't give you the info, it's very unlikely that anything else can, with the exception of some subsystems that have data-extraction tools build by the same groups that develope the kernel subsystems, for example lsm and advfs. iostat was never very useful, because nobody loved it, and sar, sigh, was a miscarriage. When I left Digital ('99) monitor was already
falling behind with respect to Tru64.
Part of the problem with collecting I/O data is that it may not be properly maintained in the kernel, which means you're SOL not matter what tool you use.
Collect is the best tool for disk I/O.
cheers,
Rob Urban
falling behind with respect to Tru64.
Part of the problem with collecting I/O data is that it may not be properly maintained in the kernel, which means you're SOL not matter what tool you use.
Collect is the best tool for disk I/O.
cheers,
Rob Urban
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-18-2005 04:58 PM
тАО09-18-2005 04:58 PM
Re: Collect I/O stats report
After a hardware & firmware upgrade and PK5 install on the system, we had some spare time in the maintenance slot.
We ran the "I/O test" described above, and with the system totally idle, we recorded a worst case of 0.55 seconds during a 45 minute test period.
I would think that this is quite high for a system without any load?
We ran the "I/O test" described above, and with the system totally idle, we recorded a worst case of 0.55 seconds during a 45 minute test period.
I would think that this is quite high for a system without any load?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-18-2005 09:49 PM
тАО09-18-2005 09:49 PM
Re: Collect I/O stats report
That's quite a better number than what you described before (between 8 and 20 seconds). I will agree with you that this is still not a number that we would like to see.
Could you give more details about the results of the test:
- You say that this is using the same test. Is this reproducable?
- Is it always on the same disk?
- Is the EMC also idle (during the maintenance window) or are other systems using it?
- Are the disks behind the LUN dedicated to the test?
- What did the EMC performance investigation reveal?
- etc.
Could you give more details about the results of the test:
- You say that this is using the same test. Is this reproducable?
- Is it always on the same disk?
- Is the EMC also idle (during the maintenance window) or are other systems using it?
- Are the disks behind the LUN dedicated to the test?
- What did the EMC performance investigation reveal?
- etc.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-02-2005 09:43 PM
тАО10-02-2005 09:43 PM
Re: Collect I/O stats report
Hi
To answer some of your questions:
- Reproducable? Kind of. Under load, we see the 8 to 20 delays, every time. Without load, we don't see these delays.
- We see this on all the disks, at different times.
- No, the EMC is busy serving other systems all the time.
- No, the disks (spindles) serve other hosts as well.
- While our test reported an I/O that took about 10 seconds to complete, the EMC test didn't show any I/O that took more than a second to be served.
This issue has been escalated within HP. We are expecting some assistance with our investigation.
I'll be sure to post our findings.
To answer some of your questions:
- Reproducable? Kind of. Under load, we see the 8 to 20 delays, every time. Without load, we don't see these delays.
- We see this on all the disks, at different times.
- No, the EMC is busy serving other systems all the time.
- No, the disks (spindles) serve other hosts as well.
- While our test reported an I/O that took about 10 seconds to complete, the EMC test didn't show any I/O that took more than a second to be served.
This issue has been escalated within HP. We are expecting some assistance with our investigation.
I'll be sure to post our findings.
- « Previous
- Next »
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