- Community Home
- >
- Storage
- >
- HPE Nimble Storage
- >
- Array Setup and Networking
- >
- Re: Windows Volume Block Size vs. Nimble Performan...
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
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
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
08-23-2013 10:24 AM
08-23-2013 10:24 AM
Hi Group,
How does the block size of a Windows volume (64kb for example) correlate with the application block sizes in Nimble Performance Policies? For example, if I used 64KB block sizes for the volumes hosting SQL logs and databases, the performance policy in Nimble for SQL is 8KB. We are beginning to reconfigure all of our volumes at 64KB as we migrate forward and I want to ensure this will not impose performance penalties when using the Nimble performance policies.
Thanks
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-26-2013 11:51 AM
08-26-2013 11:51 AM
SolutionHi Corey, welcome to NimbleConnect.
The trick when setting a block size on the storage array is to ensure that you choose a block size which is smaller than or equal to the application block size required in the host. SQL Server uses a variation of block sizes for different functions (one of them being 64K as you mention), however the smallest block size it will use is 8K and thus this is what we use as the corresponding Performance Policy block size.
I hope the above helps!
twitter: @nick_dyer_