- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: uncompress is slow for itanium server
Operating System - HP-UX
1753814
Members
7781
Online
108805
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
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
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
07-29-2009 06:50 PM
07-29-2009 06:50 PM
Re: uncompress is slow for itanium server
kenken,
Steven is of course correct, but cranky as ever. He's trying to provoke you to THINK about the data you are providing, what is happening or not happening on the systems and what might explain a difference.
Think about it... (ooops, now I did it :-)... you mentioned "3)disk io are almost the same 90%". So even is the CPU was inifinitely fast, it would seem the at best the speedup could be 10% more.... so it is the disk that defines the performance. 36MB/sec on the PA versus 27 MB/sec on the Itanium would explain it (assuming a hefty compression rate where the input IO throughput can be ignored).
Now I'll be the first to admit that there is a lot of handwaving in the above. 'disk busy' is precise, yet vague. It means there was something happening 90% of the time, but it does not mean that you might have been able to push the IO trough harder/smarter. And the actual (usermode) uncompress CPU usage is largely decoupled, hidden behind, the IO busyness.
That's why we all request more, and more precise data. How much CPU is being used ? (usermode, system). How fast is the IO subsystem... reading .. versus writing.
The 'writes' are more or less free, as long as they eventually find some time. The read speed defines whether the program has to wait for data to work on, or can keep on uncompressing, but the reads might be slowed down by the ongoing write work.
The most likely suspect (imho) is the characteristics of the IO systems provided (simple disk each?). But it could indeed still prove to be an CPU speed or porting issue. Only you can help us determine the more like cause / solution.
hope this helps some,
Hein van den Heuvel
Hvdh Performance Consulting.
Steven is of course correct, but cranky as ever. He's trying to provoke you to THINK about the data you are providing, what is happening or not happening on the systems and what might explain a difference.
Think about it... (ooops, now I did it :-)... you mentioned "3)disk io are almost the same 90%". So even is the CPU was inifinitely fast, it would seem the at best the speedup could be 10% more.... so it is the disk that defines the performance. 36MB/sec on the PA versus 27 MB/sec on the Itanium would explain it (assuming a hefty compression rate where the input IO throughput can be ignored).
Now I'll be the first to admit that there is a lot of handwaving in the above. 'disk busy' is precise, yet vague. It means there was something happening 90% of the time, but it does not mean that you might have been able to push the IO trough harder/smarter. And the actual (usermode) uncompress CPU usage is largely decoupled, hidden behind, the IO busyness.
That's why we all request more, and more precise data. How much CPU is being used ? (usermode, system). How fast is the IO subsystem... reading .. versus writing.
The 'writes' are more or less free, as long as they eventually find some time. The read speed defines whether the program has to wait for data to work on, or can keep on uncompressing, but the reads might be slowed down by the ongoing write work.
The most likely suspect (imho) is the characteristics of the IO systems provided (simple disk each?). But it could indeed still prove to be an CPU speed or porting issue. Only you can help us determine the more like cause / solution.
hope this helps some,
Hein van den Heuvel
Hvdh Performance Consulting.
- « Previous
-
- 1
- 2
- 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