- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- I/O behaviour on MSA20
Disk Enclosures
1753902
Members
9817
Online
108810
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
04-18-2008 09:59 AM
04-18-2008 09:59 AM
I/O behaviour on MSA20
I am working with a customer who has an MSA20 (12 x 750GB SATA) in a single RAID 5 config. The MSA20 is hanging off of an SA6404 in an HP DL380 G5. Using Backup Exec CPS, we noticed 2 distinct "states" that the I/O produces (using Windows 2003 perfmon):
1200 disk transfers/sec
85ms write latency
120ms read latency
17 MB/sec throughput
600 disk transfers/sec
10ms write latency
8ms read latency
72MB/sec throughput
The CPS server is doing the same job in both situations. What is the "nature" of the I/O that would cause such odd numbers? Why does only 17MB/sec cause huge delays and transfers, while 72MB/sec is fine? We haven't seen the first situation lately, it seems to have settled down a bit. Thanks for any insight.
1200 disk transfers/sec
85ms write latency
120ms read latency
17 MB/sec throughput
600 disk transfers/sec
10ms write latency
8ms read latency
72MB/sec throughput
The CPS server is doing the same job in both situations. What is the "nature" of the I/O that would cause such odd numbers? Why does only 17MB/sec cause huge delays and transfers, while 72MB/sec is fine? We haven't seen the first situation lately, it seems to have settled down a bit. Thanks for any insight.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-21-2008 12:30 AM
04-21-2008 12:30 AM
Re: I/O behaviour on MSA20
Hello J,
The states are likely because of the backup workloads. This is expected behavior in my view.
When you see lots of transfers and low throughput, Backup Exec may be backing up user shares or a source that contains smaller files. 1k to 32k or so. This is when the disk heads have to do a lot of 'seeking' which costs time.
When the amount of tranfers goes down and the throughput goes up is usually when large files are being backed up (large being multiple megabytes per file and higher)
To do some comprehensive tests, try testing with HP Library and Tape Tools. LTT allows you to build a 'known' data set on your filesystem containing known filesizes that you can use to do perfromance testing.
Note that 750GB disks are built for 'capacity' and not neccesarily for 'performance'.
Hope this brings some clarification.
-Eric
The states are likely because of the backup workloads. This is expected behavior in my view.
When you see lots of transfers and low throughput, Backup Exec may be backing up user shares or a source that contains smaller files. 1k to 32k or so. This is when the disk heads have to do a lot of 'seeking' which costs time.
When the amount of tranfers goes down and the throughput goes up is usually when large files are being backed up (large being multiple megabytes per file and higher)
To do some comprehensive tests, try testing with HP Library and Tape Tools. LTT allows you to build a 'known' data set on your filesystem containing known filesizes that you can use to do perfromance testing.
Note that 750GB disks are built for 'capacity' and not neccesarily for 'performance'.
Hope this brings some clarification.
-Eric
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