- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- EVA6000 performance
Disk Enclosures
1753479
Members
5105
Online
108794
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
тАО02-24-2011 12:52 AM
тАО02-24-2011 12:52 AM
EVA6000 performance
Hi.
I can't understand how EVA works with Windows.
I try to test EVA reading speed from Windows 2003 server. I start copy to nul process, and see 35 Mb/sec speed. EVAperf as shows about 40 Mb/sec. But when I start one more copy process it shows about 30 Mb/sec speed. EVAperf as shows 80 Mb/sec.
Why one process not use 70-80 Mb/sec?
I can't understand how EVA works with Windows.
I try to test EVA reading speed from Windows 2003 server. I start copy to nul process, and see 35 Mb/sec speed. EVAperf as shows about 40 Mb/sec. But when I start one more copy process it shows about 30 Mb/sec speed. EVAperf as shows 80 Mb/sec.
Why one process not use 70-80 Mb/sec?
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-24-2011 03:18 AM
тАО02-24-2011 03:18 AM
Re: EVA6000 performance
Performance depends on a lot of things:
- Type of disks (FATA / 10K / 15K)
- Number of disks
- RAID level (0 / 1 / 5)
- Size of the I/Os
- Secuential or random access
- Oustanding I/Os allowed by HBA driver
- Multipath software
1) A sequential read from a sigle server and typically through a single path is not a good measure of EVA performance. This system is designed to handle a lot of reads and writes from several servers. In a sequetial read test you're not going to get more speed than from a MSA or a JBOD with the same number of disks.
2) Trust EVAperf, it knows what's going on inside the EVA. Look at the latencies and amount of I/Os on the disk group
3) Changing parameters on the HBA driver, like maximum queue depth can have a big impact on maximum throughput.
- Type of disks (FATA / 10K / 15K)
- Number of disks
- RAID level (0 / 1 / 5)
- Size of the I/Os
- Secuential or random access
- Oustanding I/Os allowed by HBA driver
- Multipath software
1) A sequential read from a sigle server and typically through a single path is not a good measure of EVA performance. This system is designed to handle a lot of reads and writes from several servers. In a sequetial read test you're not going to get more speed than from a MSA or a JBOD with the same number of disks.
2) Trust EVAperf, it knows what's going on inside the EVA. Look at the latencies and amount of I/Os on the disk group
3) Changing parameters on the HBA driver, like maximum queue depth can have a big impact on maximum throughput.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-24-2011 04:41 AM
тАО02-24-2011 04:41 AM
Re: EVA6000 performance
OK. Lets discuss
Type of disks - 15K
Number of disks - maximum possible (112)
RAID level - this volume is RAID5
Size of the I/Os - whats this&
Secuential or random access - copy to nul
Oustanding I/Os allowed by HBA driver - ?
Multipath software - HPDSM with ALB
1) A sequential read from a sigle server and typically through a single path is not a good measure of EVA performance. This system is designed to handle a lot of reads and writes from several servers. In a sequetial read test you're not going to get more speed than from a MSA or a JBOD with the same number of disks.
HP-UX server with same volume makes 100 Mb/sec/ I try to understand why?
2) Trust EVAperf, it knows what's going on inside the EVA. Look at the latencies and amount of I/Os on the disk group
On evaperf all reports read latency not more then 5 ms.
3) Changing parameters on the HBA driver, like maximum queue depth can have a big impact on maximum throughput.
Max queue depth in evaperf reports is 2. It is not more then default 32.
I dont't understand one process reading speed limits
Type of disks - 15K
Number of disks - maximum possible (112)
RAID level - this volume is RAID5
Size of the I/Os - whats this&
Secuential or random access - copy to nul
Oustanding I/Os allowed by HBA driver - ?
Multipath software - HPDSM with ALB
1) A sequential read from a sigle server and typically through a single path is not a good measure of EVA performance. This system is designed to handle a lot of reads and writes from several servers. In a sequetial read test you're not going to get more speed than from a MSA or a JBOD with the same number of disks.
HP-UX server with same volume makes 100 Mb/sec/ I try to understand why?
2) Trust EVAperf, it knows what's going on inside the EVA. Look at the latencies and amount of I/Os on the disk group
On evaperf all reports read latency not more then 5 ms.
3) Changing parameters on the HBA driver, like maximum queue depth can have a big impact on maximum throughput.
Max queue depth in evaperf reports is 2. It is not more then default 32.
I dont't understand one process reading speed limits
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-24-2011 05:35 AM
тАО02-24-2011 05:35 AM
Re: EVA6000 performance
112 disks in RAID 5, and only reading data can give you a very high speed. 18000 random operations per second and 720 MB/s.
The fact that you get different results on different operating systems, while the latencies on the EVA are below 5 ms, points to a limitation on the HBA driver. The EVA is sending all the data the HBA demands, if it's not going faster is because the server is not requesting more.
I insist in that sequential read performance from a single server is not a good measure, that's not the typical usage of a shared SAN storage. You'll get the same numbers from any array with the same number of disks.
The fact that you get different results on different operating systems, while the latencies on the EVA are below 5 ms, points to a limitation on the HBA driver. The EVA is sending all the data the HBA demands, if it's not going faster is because the server is not requesting more.
I insist in that sequential read performance from a single server is not a good measure, that's not the typical usage of a shared SAN storage. You'll get the same numbers from any array with the same number of disks.
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