Show us your SSD performance

whs said:

Where is the confusion. When the 100MB partition is aligned, the rest follows. You may note that your C is 101 MBs, not KBs.

I guess I was confused by your statement here....

whs said:

1024 multiplied with any number is divisible by 4. But what does that tell me? Are you suggesting that the 101 offset of the second partition is OK?

That obviously was in response to this....

SIW2 said:

Before you do that- you need to ask:

If 1024 is divisible by 4, is 101 x 1024 also divisible by 4 ?

BTW where did I mention KB's?

whs said:

It does not matter what the spinner layout is - the SSD has to be aligned.

Ok thanks.
Then tell me this. I just did my little test. Took the image with the resized drive, which is from a 250GB drive, and loaded that on a 160GB drive.
This is what I get from DP for that drive.

DISKPART> list partition

Partition ### Type Size Offset
------------- ---------------- ------- -------
Partition 1 Primary 100 MB 1024 KB
Partition 2 Primary 60 GB 101 MB
Partition 3 Primary 87 GB 61 GB

Everything is still aligned as it was.

What is the big deal with SSDs.
Even if I first align the SSD once I load that image on it it will wipe out that 100MB partition and recreate it. Physically wiping out the alignment I just did. Right?

Well in a few days I will find out.

Thanks again. Will post back with my findings.

whs said:

Are you doing this test on a new SSD that was never aligned - only that would count. And if the first partition is aligned, the rest follows.

No I don't have it yet. But please tell me what makes SSDs so different then any other spinning drive.

As I posted above if I align the SSD then load that image on it the imaging program will WIPE out whatever partitions are already on the drive and create the new partitions as they were when the image was created.

I really don't see why this is so hard.

I guess I'm really missing something here.

As I said above, I will find out in a few days.

EDIT:
Please explain why when loading a image on a SSD that the imaging program would not PLACE that image in the exact same place on the SSD as it was on the spinner.

whs said:

Yeah, you will find out in a few days. I can only tell you what I experienced with my five SSDs. But maybe yours is different and "auto-aligns".

Please explain why when loading a image on a SSD that the imaging program would not PLACE that image in the exact same place on the SSD as it was on the spinner.

You place them as you like and as you have defined the partitions. The imaging program does nothing automatically. It puts the partition(s) to the place you direct it to.

Found this over at the Acronis forums.

For SSDs, ATI will automatically align a partition when you prepare a new disk, when you restore a single partition (case where you can resize it), and when you restore an entire disk that is aligned.
If you restore an entire disk using an image of a non-aligned disk, the restored disk will not be aligned.

If you clone a disk that is not aligned, the cloned disk will not be aligned.
If you clone a disk that is aligned, the cloned disk will be aligned.

Yet another (hopefully the definitive) SSD Alignment Thread | Knowledge Base

So I'm good to go.

Windows7 Forum SSD

I run five SDD all in Intel Raid 0, I have three 30GB OCZ Vertex as my main Windows7 system drive witch has run 24/7 for the past 16 months, it also has Ubuntu partition, my main program's run on two 60GB Vertex 2 E Intel Raid 0 on which I also store my RamDrive and VMware disks, I have all the tweaks and updated firmware, I leave prefetch alone as I don’t see any advantage to changing it the performance has stayed the same, I believe it’s because I run Diskeeper in the background and use Perfectdisk to defrag free space if performance as shown in Perfectdisk drops to 97% doesn’t show in real world and its only around once every three months, I don’t have the Windows7 100mb partition on any disks but have 1024mb offset on both SSD raids sets, I use Intel Rapid Storage driver 10.1.0.1008 and have Ghost clones of both disks touch wood not had to use them yet as Windows7 is just super stable, even though I run four raid sets with all first partition’s bootable to Windows7 and independent partitions with Ubuntu, XP64, XenServer, Windows2000 & 2003 server’s even have DOS 5.1 and 6.2 boot partitions.

My data and Backups are spread between two Seagate Barracuda 500GB Intel Raid 0 and two WD Carver Black 1TB Sata-III Marvel Raid 0 which stays in Raid 0 and can be booted to even when I break the Intel Raids in bios settings to update the SDD firmware again touch wood no data loss ever and as long as I don’t format I can flash them with the latest firmware with the OCZ tool from within Windows7/64 running on Marvel Raid array and then reset the bios to Raid and boot to them.

All in all SSD’s are well worth the effort as performance is top’s the 3x Vertex run around 65-70 second reboot with ReStarttime.vbs without Marvel Raid card connected and 80-85 second’s with, the 2x Vertex 2E run 70-75 without Marvel and 85-90 with it installed as the marvel adds around 15-20 seconds to load and check its drivers both SDD Raids score 7.9 in Windows7 performance.

Link showing my Disk Bench marks.
Link To Windows7 Performance.
Link to Restart Timer 3x Vertex Intel Raid 0 With Marvel driver installed can’t find snap without it and don’t have time to unload Marvel will post link when I have time all snaps have 90+ services running and a 3 second pause at system select screen.
Link to Restart Timer 2x Vertex 2e Intel Raid 0 Without Marvel driver installed
Link to Restart Timer 2x Vertex 2e Intel Raid 0 With Marvel driver installed
Link to Prime95 Bench-test
Link to System Temps Intel Burn-Test 64, 21-22 x 201MHz = 4400MHz Max with C1 stepping, Memory is GT 2000 8-8-8 24 but run 24/7 with 6-6-6 16 @800MHz runs 24/7 Hyper/Turbo/Stepping Enabled

whs said:

Shootist said:

Found this over at the Acronis forums.

For SSDs, ATI will automatically align a partition when you prepare a new disk, when you restore a single partition (case where you can resize it), and when you restore an entire disk that is aligned.
If you restore an entire disk using an image of a non-aligned disk, the restored disk will not be aligned.

If you clone a disk that is not aligned, the cloned disk will not be aligned.
If you clone a disk that is aligned, the cloned disk will be aligned.

Yet another (hopefully the definitive) SSD Alignment Thread | Knowledge Base

So I'm good to go.

This is good to know. I never used Acronis on an SSD - just years ago on spinners.

Well I would think any UP TO DATE imaging program would handle this the same way.
That is taking a image of the COMPLETE DRIVE, not just individual partitions even if you did all partitions on the drive one by one, and restoring that COMPLETE image.

I think the problems started when people just imaged the system/boot partitions and then tried to restore them to a SSD. Acronis even states in that case the offset will not be correct. Without first aligning the drive.

Actually I can't wait to get this new SSD and most of all see how the imaging goes. I'll know Wednesday night.