IOMeter – Average Transaction Time (rev 1)
Back with the Kingston SSDNow V Series 40GB review, I revised the layout of these graphs to better show SSD latency and access time. First, I have removed HDD results as they throw the scale too far to tell any meaningful difference in the SSD's you are trying to focus on. Second, I have reduced the queue depth scale down to 4. In practical terms of a running OS, queue depth is how many commands are 'stacked up' on the SSD at that time. An SSD is so fast at servicing requests that typical use will rarely see it increasing past 4. In the cases where it does, there is so much going on that you are more concerned with IOPS and throughput at that point than transaction time. The below charts are meant to show how nimble a given SSD is. Think of it as how well a car handles as opposed to how fast it can go.
Some notes for interpreting results:
- Times measured at QD=1 can serve as a more 'real' value of seek time.
- A 'flatter' line means that drive will scale better and ramp up its IOPS when hit with multiple requests simultaneously.
Very thorough review Allyn.
Very thorough review Allyn. The move to try out the new flash size using sandforce instead of Indilinx perplexed me at first, but then I thought that they would probably want to experiment the hardware change with a tried and true firmware.
looks great nice work Allyn!
looks great nice work Allyn! Though you should really include more 500+ gb units in your reviews for completeness 😀
Thanks! We usually try to
Thanks! We usually try to cover ranges, but the 3.20 is not available in a >240GB capacity.
I am still using my OCZ
I am still using my OCZ Vertex 3 SSD with no problems. Vertex 3.20 does not deserve that Vertex name. Come on, OCZ, you need to do better SSD Vertex SSD products.
Hey Allyn,
What components
Hey Allyn,
What components make up the overhead that prevents SSD’s from reaching the max 6gbps bus speed? Is it all scsi frame overhead or are there other limiting factors?
Thanks.