- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- Re: EVA8400 and fine tuning of Cache Policies
HPE EVA Storage
1753665
Members
6100
Online
108798
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
тАО12-08-2009 09:56 AM
тАО12-08-2009 09:56 AM
Hi All,
Has anyone fine tuned their EVA cache policies? Any performance benefits?
We have an EVA8400 with 22GB cache but still we utilize the default Cache Policies for the luns, i.e.
Read Cache: On
Mirror Cache: Mirrored
Write Cache: Requested:Write-Back
Actual: Write-Back
Could anyone explain the benefit of the default cache policies?
Are these policies good for a big cache EVA like the EVA8400?
Many thanks again for your help.
Kind Regards,
Charlie
Has anyone fine tuned their EVA cache policies? Any performance benefits?
We have an EVA8400 with 22GB cache but still we utilize the default Cache Policies for the luns, i.e.
Read Cache: On
Mirror Cache: Mirrored
Write Cache: Requested:Write-Back
Actual: Write-Back
Could anyone explain the benefit of the default cache policies?
Are these policies good for a big cache EVA like the EVA8400?
Many thanks again for your help.
Kind Regards,
Charlie
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-09-2009 07:11 PM
тАО12-09-2009 07:11 PM
Solution
Hello Charlie,
Yes, default cache policies are the best for better performance and redundancy. Here are the explanations of these settings:
read caching
A cache method used to decrease subsystem response times to a read
request by allowing the controller to satisfy the request from the cache
memory rather than from the disk drives. Reading data from cache memory is
faster than reading data from a disk. The read cache is specified as either On
or Off for each virtual disk. The default state is on.
write back caching
A controller process that notifies the host that the write operation is complete
when the data is written to the cache. This occurs before transferring the
data to the disk. Write back caching improves response time since the write
operation completes as soon as the data reaches the cache. As soon as
possible after caching the data, the controller then writes the data to the
disk drives.
mirrored caching
A process in which half of each controller├в s write cache mirrors the companion
controller├в s write cache. The total memory available for cached write data is
reduced by half, but the level of protection is greater.
Regards
Susanta
Yes, default cache policies are the best for better performance and redundancy. Here are the explanations of these settings:
read caching
A cache method used to decrease subsystem response times to a read
request by allowing the controller to satisfy the request from the cache
memory rather than from the disk drives. Reading data from cache memory is
faster than reading data from a disk. The read cache is specified as either On
or Off for each virtual disk. The default state is on.
write back caching
A controller process that notifies the host that the write operation is complete
when the data is written to the cache. This occurs before transferring the
data to the disk. Write back caching improves response time since the write
operation completes as soon as the data reaches the cache. As soon as
possible after caching the data, the controller then writes the data to the
disk drives.
mirrored caching
A process in which half of each controller├в s write cache mirrors the companion
controller├в s write cache. The total memory available for cached write data is
reduced by half, but the level of protection is greater.
Regards
Susanta
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-11-2009 09:04 AM
тАО12-11-2009 09:04 AM
Re: EVA8400 and fine tuning of Cache Policies
Hi Susanta,
Our HP storage specialist also has confirmed the same thing that the default cache policy is better for us, and generally for most requierements.
Many Thanks.
Charlie
Our HP storage specialist also has confirmed the same thing that the default cache policy is better for us, and generally for most requierements.
Many Thanks.
Charlie
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