| By Peter Velikin | Article Rating: |
|
| January 21, 2013 01:30 PM EST | Reads: |
1,861 |
File System Alignment for SSDs
There are many techniques and methods that can be used to tune an IT system to improve overall system performance. SSD caching is widely being used as a low cost, easy to implement method to quickly increase performance with little or no impact on existing operations. One thing that needs to be considered when choosing SSD caching is how to configure a file system to maximize the performance increase SSD caching provides.
Operating Systems and Block Size
In the past few years, the sector size of HDDs has increased from 512 bytes to 4k bytes. Relatively new operating systems (e.g. Windows Server 2008 R2 to present) have evolved to work with this not-so-new sector size to take advantage of higher density drives. Problems, however, can occur for older operating systems that were not designed to work with the larger block size devices. This becomes a critical issue when SSDs are introduced into the mix. SSDs are all designed to operate with a 4k block size (block and sector are used interchangeably). As a result, IT managers buying SSDs to improve system performance may not be getting the most out of their new, relatively expensive investment. Proper alignment of the file system may help to get better performance in this case.
Some Points to Consider Regarding Block Size and Alignment
Here are some things you should consider when using SSDs and modern HDDs in your system:
- Block size – always use 4k block size
- Block alignment – needs to be set to 4k. If the blocks are not 4K aligned, there is additional disk I/O overhead because 2x blocks need to be fetched for every access.
- Partition alignment – Ensure that the starting partition is aligned to 4k. If your system was upgraded from pre-Windows 2008 R2 OS, make sure you re-align the partitions to 4k.
- Memory allocation (Linux only - no control on Windows) [I could not figure out what to write about this]
- VMware environments – align all guest data disks on 4k boundaries
- Hyper-V – align all guest data disks on 4k boundaries
Best Practices Results
Optimizing your system according to the above recommendations can improve performance up to 50%. Most modern OS file systems use these methods by default so there is no need to do anything. XFS and Windows versions earlier than Windows 2008R2 do not do this alignment automatically.
Velobit HyperCache caching software operates based on 4k blocks. If your existing system is not set up to work this way, Velobit will still work with the different block size making Velobit an ideal way to get performance improvement for older, legacy systems. However, the performance increase provided by Velobit will be limited due to additional overhead associated with managing non-4k block sizes.

Read the original blog entry...
Published January 21, 2013 Reads 1,861
Copyright © 2013 SYS-CON Media, Inc. — All Rights Reserved.
Syndicated stories and blog feeds, all rights reserved by the author.
More Stories By Peter Velikin
Peter Velikin has 12 years of experience creating new markets and commercializing products in multiple high tech industries. Prior to VeloBit, he was VP Marketing at Zmags, a SaaS-based digital content platform for e-commerce and mobile devices, where he managed all aspects of marketing, product management, and business development. Prior to that, Peter was Director of Product and Market Strategy at PTC, responsible for PTC’s publishing, content management, and services solutions. Prior to PTC, Peter was at EMC Corporation, where he held roles in product management, business development, and engineering program management.
Peter has an MS in Electrical Engineering from Boston University and an MBA from Harvard Business School.
- Cloud People: A Who's Who of Cloud Computing
- Windows Azure IaaS Reaches General Availability
- Portable Experimenter’s Platform, Powered by Raspberry Pi
- Session Topics: 12th Cloud Expo / Cloud Expo New York
- Ubuntu-based Open Source Linux Mint Tests KDE Version
- AMAX Launches StorMax(TM) CFS, powered by IBM(R) General Parallel File System(TM) (GPFS(TM))
- NIST to Sponsor FFRDC Widespread Adoption of Integrated CyberSecurity
- Project Floodlight Grows to the World’s Largest SDN Ecosystem; Global Users, Contributors and Partners Innovating Using Open Source SDN
- Red Hat Hires Azure Guy to Run Virtualization
- Mobility News Weekly – Week of March 17, 2013
- HotLink Debuts Amazon EC2 Plug-in for Microsoft SCVMM with Latest Release of HotLink Hybrid Express
- Rackspace and Red Hat Celebrate Victory over Troll
- Cloud People: A Who's Who of Cloud Computing
- Windows Azure IaaS Reaches General Availability
- Portable Experimenter’s Platform, Powered by Raspberry Pi
- SUSE Receives Common Criteria Security Certifications
- Session Topics: 12th Cloud Expo / Cloud Expo New York
- Red Hat Unveils Big Data and Open Hybrid Cloud Direction
- Granular Enforcement of Access to File Systems Featured in Latest Release of FoxT ServerControl
- Ubuntu-based Open Source Linux Mint Tests KDE Version
- Red Hat Spin-Off Simplifies Orchestration
- AMAX Launches StorMax(TM) CFS, powered by IBM(R) General Parallel File System(TM) (GPFS(TM))
- NIST to Sponsor FFRDC Widespread Adoption of Integrated CyberSecurity
- Project Floodlight Grows to the World’s Largest SDN Ecosystem; Global Users, Contributors and Partners Innovating Using Open Source SDN
- The i-Technology Right Stuff
- After Ubuntu, Windows Looks Increasingly Bad, Increasingly Archaic, Increasingly Unfriendly
- Linux.SYS-CON.com Exclusive: Linus Discloses *Real* Fathers of Linux
- A Closer Look at Damn Small Linux
- Linus' Top Ten SCO Barbs
- SCO CEO Posts Open Letter to the Open Source Community
- Netscape Co-Founder's 12 Reasons for Growth of Open Source
- Where Are RIA Technologies Headed in 2008?
- *POINT - COUNTERPOINT SPECIAL* What's Wrong with the Open Source Community?
- Introducing "Cooperative Linux" - Linux for Windows, No Less
- Linux.SYS-CON.com Exclusive: What Would UserLinux Look Like?
- Why Recovering a Deleted Ext3 File Is Difficult . . .


























