- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- Re: Read and write cache settings for FATA
Disk Enclosures
1752677
Members
5322
Online
108789
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
Go to solution
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-01-2011 05:39 AM
тАО04-01-2011 05:39 AM
EVA 8100; xcs 6.220; Command View EVA 9.3
Despite having 78 disks in FATA storage group, it doesn't take much IO (particularly writes) to overwhelm the FATA disks and get the queue depth rising. Ultimately this affects overall EVA latency since the IO requests are all bunched together for both FATA and FC disk groups.
Would setting the read cache to "off" and/or setting the write cache to "write-through" help or hinder with this?
It seems that the best solution would be if HP had a firmware update to separate the IO requests between disk groups such that FC requests never wait on FATA.
Despite having 78 disks in FATA storage group, it doesn't take much IO (particularly writes) to overwhelm the FATA disks and get the queue depth rising. Ultimately this affects overall EVA latency since the IO requests are all bunched together for both FATA and FC disk groups.
Would setting the read cache to "off" and/or setting the write cache to "write-through" help or hinder with this?
It seems that the best solution would be if HP had a firmware update to separate the IO requests between disk groups such that FC requests never wait on FATA.
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-01-2011 06:43 AM
тАО04-01-2011 06:43 AM
Re: Read and write cache settings for FATA
I think setting the write cache to "write-through" for FATA vdisks would cause the server writing to a FATA vdisk to be slowed down from writing too fast and therefore save the rest of the EVA from getting backed up behind the FATA requests. Does that make sense?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-01-2011 07:36 AM
тАО04-01-2011 07:36 AM
Solution
Yes, in theory. But without wbc, the virtual disks become _awful_ slow.
I had such a case were the customer was too eager to have "cheap storage" and he bought 10 FATAL disk drives for each of his EVAs. Then he was dumping multiple TeraBytes from multiple databases each night.
After some time the problems you mention came up. I was asked for help and did some little analysis with EVAperf and TLVIZ.
When we turned of the WBC, the whole backup did not finish in time and latencies where *horrible*.
To keep the story short:
additional Data Protector licenses were bought to save the databases directly to tape. All FATAL disk drives were thrown out and replaced with smaller FC disks drives. Those were added to an existing disk group for additional storage requirements.
"Friends, don't let your friends use FATAL disk drives!"
I had such a case were the customer was too eager to have "cheap storage" and he bought 10 FATAL disk drives for each of his EVAs. Then he was dumping multiple TeraBytes from multiple databases each night.
After some time the problems you mention came up. I was asked for help and did some little analysis with EVAperf and TLVIZ.
When we turned of the WBC, the whole backup did not finish in time and latencies where *horrible*.
To keep the story short:
additional Data Protector licenses were bought to save the databases directly to tape. All FATAL disk drives were thrown out and replaced with smaller FC disks drives. Those were added to an existing disk group for additional storage requirements.
"Friends, don't let your friends use FATAL disk drives!"
.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-01-2011 07:40 AM
тАО04-01-2011 07:40 AM
Re: Read and write cache settings for FATA
I'm ok with the FATA vdisks being _awful_ slow if it guards the EVA from high latency. Seems like the lesser of evils to me.
Thanks for the insightful reply!
Thanks for the insightful reply!
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