- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- Re: EVA 4400 / Windows 2008 Cluster / MPIO using H...
Disk Enclosures
1753575
Members
6075
Online
108796
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
тАО05-07-2009 08:21 AM
тАО05-07-2009 08:21 AM
EVA 4400 / Windows 2008 Cluster / MPIO using HP DSM
Hi,
We have a EVA4400 access by a 2 node windows 2008 cluster.
We have 48disk / 1 storage group / 1 vdisk (RAID10). The I/O profile is mixed between random (50%) and sequential IO (50%).
I believe that the deployment has been made without any extra configuration on any subsystems.
Workload is SQL server 2008.
We are noticing spikes of 3000 write operations/sec, what is concerning is the read latency spiking to 160ms. I would have thought in the RAID configuration above that we would be able to sustain the write operations with less latency.
I was wondering if anyone could advise on general configuration settings on the storage/HBA/switch/DSM to alleviate what appears to be a performance bottleneck.
I appreciate any advise people may wish to give!
Thanks
Matthew
We have a EVA4400 access by a 2 node windows 2008 cluster.
We have 48disk / 1 storage group / 1 vdisk (RAID10). The I/O profile is mixed between random (50%) and sequential IO (50%).
I believe that the deployment has been made without any extra configuration on any subsystems.
Workload is SQL server 2008.
We are noticing spikes of 3000 write operations/sec, what is concerning is the read latency spiking to 160ms. I would have thought in the RAID configuration above that we would be able to sustain the write operations with less latency.
I was wondering if anyone could advise on general configuration settings on the storage/HBA/switch/DSM to alleviate what appears to be a performance bottleneck.
I appreciate any advise people may wish to give!
Thanks
Matthew
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-07-2009 09:27 AM
тАО05-07-2009 09:27 AM
Re: EVA 4400 / Windows 2008 Cluster / MPIO using HP DSM
A few questions first:
- What kind of drives? in VRAID 1 you can expect 115 Iops per drive with 15k FC drives, and half that when using FATA drives
- Only one LUN? Many HBA drivers and operating systems have a limited queue per LUN, so all I/Os go to a single queue of 16 or 64 for example.
- Even with 48 disks, 3000 Iops mean 125 Iops per drive in VRAID 1
- MPIO set to load balance on all paths?
- What kind of drives? in VRAID 1 you can expect 115 Iops per drive with 15k FC drives, and half that when using FATA drives
- Only one LUN? Many HBA drivers and operating systems have a limited queue per LUN, so all I/Os go to a single queue of 16 or 64 for example.
- Even with 48 disks, 3000 Iops mean 125 Iops per drive in VRAID 1
- MPIO set to load balance on all paths?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-08-2009 12:16 AM
тАО05-08-2009 12:16 AM
Re: EVA 4400 / Windows 2008 Cluster / MPIO using HP DSM
Hi,
here is the bunch of sizing tools for your inspiration:
http://h71028.www7.hp.com/enterprise/cache/576785-0-0-225-121.html?jumpid=reg_R1002_USEN
here is the bunch of sizing tools for your inspiration:
http://h71028.www7.hp.com/enterprise/cache/576785-0-0-225-121.html?jumpid=reg_R1002_USEN
the pain is one part of the reality
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-08-2009 01:47 AM
тАО05-08-2009 01:47 AM
Re: EVA 4400 / Windows 2008 Cluster / MPIO using HP DSM
Hi Guys,
Thanks very much.
It is possible that the queueing for the single LUN is causing the problem. Although it looks like we may just be topping out the IOP capacity on the diskset.
To degate any queueing issues, we are going to split into seperate LUNs and spread the datagroups across those.
Thanks again for your assistance, I will update and let you know how we are coming along.
Regards
Matthew
Thanks very much.
It is possible that the queueing for the single LUN is causing the problem. Although it looks like we may just be topping out the IOP capacity on the diskset.
To degate any queueing issues, we are going to split into seperate LUNs and spread the datagroups across those.
Thanks again for your assistance, I will update and let you know how we are coming along.
Regards
Matthew
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