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.
Coupled with the very high IOPS figures at lower queue depths, Vector turns in some impressively low latencies. They are in fact the lowest we've ever seen from *any* SATA solution.
I want one. Or two. Set me
I want one. Or two. Set me up, Allyn. I promise that I will make it worth your while in Vegas at CES.
Seems pretty awesome, I
Seems pretty awesome, I wonder how the 128GB version performs compared to the 128GB vertex 4 (was planning on getting vertex 4 before I saw this)
From what I’ve seen of the
From what I've seen of the specs, they should be pretty close. I've requested the smaller capacity for further evaluation towards this end.
Any idea if the Arm Core is
Any idea if the Arm Core is based on the A15?