- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- MSA Storage
- >
- 4KB boundaries and proper block size for SSDs
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
10-12-2018 07:58 AM
10-12-2018 07:58 AM
When reviewing the MSA 2050 SMU reference guide I noticed this tidbit in relation to SSDs and write amplification. It states that
Data that is written in sequential LBAs that are aligned on 4KB boundaries results in the best write amplification factor. The worst write amplification factor typically occurs for randomly written LBAs of transfer sizes that are less than 4KB and that originate on LBA's that are not on 4KB boundaries. Try to align your data on 4KB boundaries
When it states "4KB" boundaries, is it referring to a block size of 4KB? Does that mean that the block size, or "allocation unit size" as Windows calls it should be 4KB? Or would a multiple of 4KB, such as 8KB, 64KB, etc, work? I'm looking to build a few archive LUNs with archive affinity for our larger file servers that just have data sitting there, and with 4KB block size I can only get the LUNs up to 16TB in Windows. I know that with archive affinity it shouldn't write to the performance tier at all, but I may at some point want a larger-than-16TB volume for performance data as well.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-14-2018 06:40 PM
10-14-2018 06:40 PM
SolutionI would suggest you to refer the below link and check "Sector format" and "Chunk Size",
https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-c05075467
I would suggest to keep in mind when creating Virtual Disk Group, number of drives and Chunk size selection. Please find some important notes from SMU guide,
"NOTE: For a virtual group, the system will use one of the following chunk sizes, which cannot be changed:
– RAID 1: Not applicable
– RAID 5 and RAID 6:
• With 2, 4, or 8 non-parity disks: 512k. For example, a RAID-5 group with 3, 5, or 9 total disks or a RAID-6 group with 4, 6, or 10 total disks.
• Other configurations: 64k
– RAID 10: 512k"
So yes the size of data that you are transferring from Host is important to decide on chunk size on MSA. This is why we say data alignment should be 4KB boundaries.
Hope this helps!
Regards
Subhajit
If you feel this was helpful please click the KUDOS! thumb below!
***********************************************************************************
I work for HPE
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-24-2018 01:12 AM
10-24-2018 01:12 AM
Re: 4KB boundaries and proper block size for SSDs
Can you please help us to understand if the issue got resolved or not?
If issue got resolved then how?
This will help for everyone who are all following your forum.
Hope this helps!
Regards
Subhajit
If you feel this was helpful please click the KUDOS! thumb below!
***********************************************************************************
I work for HPE
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-24-2018 07:00 AM
10-24-2018 07:00 AM
Re: 4KB boundaries and proper block size for SSDs
Sorry, I'm having a bit of difficulty with this website. It looks like I'm finally able to login and type in the text box (it kept disappering).
This information seems to be the most pertinent that I have found. I've been settling on setting the block size for Windows-based LUNs to the default 4k and the block size for ESXi to the only selectable option in the drop down (1MB).