- Community Home
- >
- Storage
- >
- HPE Nimble Storage
- >
- Array Performance and Data Protection
- >
- missing cache hits
Categories
Company
Local Language
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
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
Community
Resources
Forums
Blogs
- 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-17-2014 10:53 PM
тАО12-17-2014 10:53 PM
i am doing 9 concurrent svmotion to a nimble volume from a emc cx and notive that cache hits a getting missed and going as low as 80%. any idea whats going on?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-18-2014 06:47 AM
тАО12-18-2014 06:47 AM
SolutionHello Tony,
When you perform sequential writes to a Nimble system (in this instance, a Storage vMotion) we automatically bypass writing data into cache, as we cannot have a good idea as to whether the data is hot or not. Therefore what the array does is after the data is on the system the array figures out what data is needed for cache and will pre-fetch copy blocks as and when required.
This is why you're seeing lower cache hits as the data migrated to Nimble is cold, however what you should notice is this warm back up within a few minutes or so.
twitter: @nick_dyer_
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-28-2014 12:55 AM
тАО12-28-2014 12:55 AM
Re: missing cache hits
Hi,
this could be solve with performance policy tuning :
Enable
perfpolicy --edit name --cache_policy aggressive
Disable
perfpolicy --edit name --cache_policy normal
please refer in documentation before ( nice document of BP Nimble + vmware)
thanks
Dima
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-28-2014 11:10 AM
тАО12-28-2014 11:10 AM
Re: missing cache hits
Dmitry Marevutsky wrote:
Hi,
this could be solve with performance policy tuning :
Enable
perfpolicy --edit name --cache_policy aggressive
Disable
perfpolicy --edit name --cache_policy normal
please refer in documentation before ( nice document of BP Nimble + vmware)
thanks
Dima
I'd be very careful enabling Aggressive Caching on any array - in fact it should only be done under the guidance and/or instruction of Nimble Storage Support or Systems Engineers for specific workloads or requirements.
It's hidden in the CLI for a reason; it's not a tool for everyday use and has the power to be detrimental to your storage array caching if not used wisely.
In this case (standard Storage vMotions) Aggressive Caching should NOT be enabled.
twitter: @nick_dyer_