Sequential, streaming operation effectively does not suffer from misaligned sectors at all.
I am wondering what will happen when a disk fails in an array and one member is replaced by it's 4KB counterpart ? This might mean that loads of us have to stock up on "old" disks before this transition is finalized !
And vot is Linux, chopped liver?http://www.osnews.com/story/22872/ [...] ard_DrivesMaXX99, AIU if you replace a drive the array *may* get slow on writes to that drive, depending on the established alignment of that drive. It may be possible to use a different, proper align on the new drive when it is added.
I wonder how much of a boost SSDs will get from the new 4KB blocks?
@LuckyDucky7: since LBA in SSD is emulated anyway (they need to write by 512 _K_b increments), the only boost you'd get would be in capacity.As for XP users, the only problem is when they create a partition from inside the installer - creating a NTFS partition with, say, a Ubuntu LiveCD, and then installing XP would solve the problem.
So in the applications performance test 512byte sectors are superior then 4kb sectors, but 4kb sectors are slightly better then 512byte sectors in the gaming performance test. So it's basically becomes pro or con depending upon what software you use your hard drive for the most
I too was curious about the PS3 use of 4k sectors. Since all new HDDs going forward are going to be 4k, if I wanted to upgrade my PS3 HDD, how would that work? If I pop the drive in and have the PS3 set it up and install the system software will it be unaligned? Will I have to put it in my PC first and partition it / align it, then put it in the PS3? Will the PS3 recognize it after this is done? So many questions. Hey Toms, can u do some test with the PS3 and these 4K drives and let us know what you find? Maybe even the Xbox too.
The issue with these drives are that they do not seem to work well in lots of NAS-drives aswell they have huge performance problems in RAID-arrays. I have had immense problems with getting them to work in RAID5.This will have abig impact on people migrating/exchanging older 512 byte sector drives to new 4096 byte ones.You need to align not just to sector size but also to RAID stripe size. None of the free alignment tools enables you to do custom alignment on drives in raid-arrays. (Yes I have tried Paragon Alignment Tool and Acronis aswell). THG should write an article about that The larger issue is that we need a BIOS and OS that can handle different sector size aswell as handle large drives (
I think SSDs have a different size sector aswell so they need to be aligned for good performance? THG should write an article dealing with the implications of the storage limitations of the BIOS and OS and the implcations it has for customers. This to raise the awareness and also pressure manufactures to deal with it The issues I refer to are the BIOS limitations of fixed sector size and a maximum drive size of 2.1TB.
I've not seen any information what cluster size was used when formatting with NTFS. The default is 512 byte, which is obviously sub-optimal if the hardware sector size is 4kb.Using a 4kb cluster size in NTFS should produce much better results.
beign a gamer that is stil too borke to afford win 7 (im stilon xp) i dont think it would, given the conclusion , i guessing it wont afect my gaming much really, but as a student majoring in game art design i have to wonder how it wil affect programs such as , 3ds amx ,maya, photoshop ,UDK, or source hamer editor. ? might you guys at toms consider testing these apps in xp with the differnt hard drives ?
wow this is a good article.
Does anybody know how I can tell the difference between drives with 512 byte sectors and 4 KB sector? I didn't see markings indicating either on the older and newer drive pictures.
On page 6 there is a typo at the bottom. "Workloads that do not involve read operations, such as the Web server test pattern, don’t show any disadvantage at all in I/O testing" should say "write operations". There was another typo earlier in the article which I will now try to locate.