A
However, this does not apply to SSDs since they don't spin. 40GB SSD is as fast as 480GB one with the same controller. Amount of NANDs may affect the speed but usually they don't.
This can be true for the most part if lower density nands are used instead of less nands.
ie the intel SSDs show this. the 160 is faster than the 80 which is faster than the 40, simply because they didn't fill the nand slots and left them empty. I'm not sure how the mba ones work, as I think the 256 would have more nand modules than the 128 and perhaps the 64, but we'd have to tear it open to see...
Then again the nand modules could be slower at higher capacities etc, so it is difficult to say for sure, unless we test.
So far it seem the AX ssds have higher read and write speeds than the CJ models.
But I'm actually curious about the random read and write 4k and such blocks. While numbers for continuous read and write are nice, the random read and write seem to contribute more to my day to day usage patterns. ie I have an intel 80gb x-25m G2, which read: 250mb/sec and write 70mb/sec advertised... and an OCZ agility 2 sandforce drive with read: 285mb/sec write 275mb/sec... in theory the sandforce SSD should blow away the intel drive. what I've actually seen is on the same computer, the intel drive boots faster, and gets a higher windows disk score (7.7) where the sandforce drive gets a 7.4 and boots about 1 second slower. Crystal disk benchmarks also show while the sequential speeds are faster on the sandforce drive, the intel drive is faster in random reads/writes. Don't get me wrong. the sandforce drive is still really fast, but I think that read/write numbers don't always mean much if we don't look at random small file read/writes.
Does any one have benchmarks for either CJ or AX ssds? My 128gb ultimate 11 inch uses the CJ ssd.
Also the native command queuing might play a role... here's something from wiki
NCQ is also used in newer solid-state drives where the drive encounters latency on the host, rather than the other way around. For example, Intel's X25-E Extreme solid-state drive uses NCQ to ensure that the drive has commands to process while the host system is busy processing CPU tasks. [3]
NCQ also enables the SSD controller to complete commands concurrently (or partly concurrently, for example using pipelines) where the internal organisation of the device enables such processing.
For example, the SandForce 1200[4] based OCZ Vertex II 50GB drive running on a Dell Perc 5i (which doesn't support SATA NCQ) delivers about 7,000 4k IOPS (50% write) at a controller queue depth of 32 IOs. Moving the drive to the similar Dell Perc 6i increases this to over 14,000 IOPS on the same basis