You're kind of contradicting yourself. On the one had your implying it's all a bit too complicated and on the other your asking for explanations of all the complex stuff which you really don't need to know. You shouldn't have to do anything special with the drives if you don't want to. If you install Windows Vista or 7 on them they are automatically aligned. If you install Windows 7 on them it SHOULD disable superfetch, defrag and drive indexing for you (though it didn't for me). So I'm not asking you to take my word for it - Microsoft have determined these settings produce the optimal performance on SSD's. So it's down to taking their word for it and if you want to understand the reasoning you need quite a bit of research into how these things work which may be beyond what I can get across in a forum post but I'll have a go!
Alignment.
At a physical level the drives store their data in 4k pages within 512k erase blocks on the disk. NTFS also stores it's files in 1 or more 4k clusters. Now, imagine you need to read a 4k cluster. If your operating systems partition is correctly aligned with the drive you simply read a 4k page off the drive. If however it is not then you have to read 2 x 4k pages for every 4k cluster you need to read. If your partition was created by the Vista or Win7 setup then your alignment is fine. If your partition was created by XP or older then the alignment is wrong. If you restored a disk image backup to the partition then it could go either way depending on the backup software and settings used.
Superfetch and Drive Indexing and Prefetching are disk caching techniques. They keep a track of files you regularly use and try to load them up in advance into memory on the grounds that memory is much faster than hard disks. However, they provide no performance benefits for SSD's because SSD's are so fast anyway and they, as mentioned above use up memory doing what they do. They also write frequent usage statistics to the disk so they can track commonly used programs to allow them to do their job. So they don't speed SSD's up, use up memory and waste SSD erase cycles.
Defrag.
The point of defragmenting files is to ensure that all parts of a file are consecutive on a disk. The reason for this is that mechanical drives have a seek time of say 10ms to physically move the read head to another part of the disk. If it has to do this a lot because a file is in bits all over the disk then this will hurt performance. However SSD's have a seek time of something like 0.1ms so can more or less instantly get all the bits of a file near instantly no matter where it is - especially when backed up with a 64mb cache. So again, defrag provides no SSD benefits but has a downside to it. Namely defragging a drive involves a LOT of rewriting on the drive which again wastes erase cycles.
Trim and Garbage Collection
When you delete a file the file is not actually deleted but instead just marked as deleted. This is a technique to speed up deletes on mechanical drives and is why secure erase utilities exist to actually delete them. However, whereas mechanical drives can simply overwrites existing files - SSD's cannot. The file has to be erased first so overwriting a previously deleted file is slower than writing to an empty part of the disk. To resolve this, Trim was born. Trim is a command sent form the operating system to the SSD when you delete a file to actually erase the file rather than just mark it as deleted.
Garbage Collection does a similar job but the disk itself works out what's deleted whenever it is idle and cleans the drive up independent of the operating system. The main advantage of this is it works on older operating systems that do not support Trim but it again causes wear on the drive.
For Trim to work requires operating system support (Windows 7), drive support (the latest firmware) and storage controller support (currently - pretty much only the ones built into Windows 7). At the moment 3rd party drivers for raid controllers don't support it but they are likely to soon.
![[URL]](http://www.forum.crucial.com/skins/images/88446EE8FCCED8821BE340C5AA4123A4/base/images/message_has_url.png "Contains a hyperlink")
