I have a 64 GB SATA III SSD in my home desktop PC (see bottom for specs) with Windows7 enterprise installed. I have the OS and programs stored on the SSD and all my data on a second 2TB HDD, however due to Microsoft/Adobe updates, I now have only 4GB left on the drive and was planning on expanding the drive by buying either 1 more SSD and doing RAID0 or 2 more SSDs and doing RAID5. First, before you all try to convince me never to do RAID0, since I store all my data on a second drive (and even changed the user profile folder to be the root of that drive) and plan on imaging the SSD drive after all programs are installed, I could care less if I lost all data on the SSD drive array. But I do have two sets of questions:
1. I have read about the garbage collection problem and lack of TRIM support on hardware raid controllers, but is this an issue with Windows volume management software RAID? Will performance significantly improve with controller RAID? Will drive life significantly improve with TRIM/garbage collection support if available in software RAID? This will answer if controller or software RAID better with SSD.
2. I see "60GB" and "64GB" drives and was wondering if these are the same real capacity with different labels, or actually different capacity, especially if doing a RAID5 set up where this matters more. I searched and searched but did not find evidence of this one way or the other, the best I can tell is that write amplification over provisioning
may have something to do with different labeling of drive capacity, but can anyone provide proof of whether a "60GB" SSD drive is equal or not to a "64GB" SSD drive, and would I loose capacity if I mixed them in a RAID array?
Crucial CTFDDAC064MAG-1G1 RealSSD C300 2.5" Solid State Drive
AMD Six Core 4.0GHz Overclocked Barebone PC
- ASUS M4A89GTD PRO/USB3