Corsair introduces the Neutron Series SSD

Loading...

Been waiting a while? Get Flash to see this player.

Fourth-generation drive eschews SandForce in favour of Link_A_Media Devices.

Related Reading


HEXUS Forums :: 4 Comments

Login with Forum Account

Don't have an account? Register today!
I don't understand how SATA 3 has limited bandwidth of <600mb/sec when if you raid 0 a Force GT you can achieve read and write over 1GB/sec. Surely the best option is to make drives that are designed with RAID 0 in mind and maybe have two drives stuck together but feed into two SATA 3 ports.
Brewster0101
I don't understand how SATA 3 has limited bandwidth of <600mb/sec when if you raid 0 a Force GT you can achieve read and write over 1GB/sec. Surely the best option is to make drives that are designed with RAID 0 in mind and maybe have two drives stuck together but feed into two SATA 3 ports.

Because when you do RAID it is operating over 2 channels, one to each drive, the limit then becomes how much data the RAID chip and the CPU it uses (host or dedicated on high end RAID cards) can munch through.
Brewster0101
I don't understand how SATA 3 has limited bandwidth of <600mb/sec when if you raid 0 a Force GT you can achieve read and write over 1GB/sec. Surely the best option is to make drives that are designed with RAID 0 in mind and maybe have two drives stuck together but feed into two SATA 3 ports.

The main problem I can think of with that is that RAID controllers (at the moment) can't pass the TRIM command to the SSD, so you don't get to use TRIM. I know that there are some controllers (thinking that the one on the latest (I think) Revo drive allowed a specific TRIM command through) which can do it, but on the example I mentioned it required a different command to normal which Windows 7 (or earlier) couldn't give.
Does this mean that the drives will allow Trim support when two are used in raid? Or is that down to the mobo/chipset?