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.
It’s just simple (inverse) math at this point. Drives that perform at lower IOPS will have latencies at the higher ends of these scales.
Hi Allyn & crew,
Nice review,
Hi Allyn & crew,
Nice review, but have you ever tested any IDE (PATA) SSDs? I bought a RunCore SSD (Model 0900027140 32GB)and have tried almost everything (I get a BSOD) and can only get into the Safe Mode. I know IDE is old, but I was trying use one in an old SONY PCG-V505DC1 laptop and have never been able to boot into Windows XP. Whether I start with a fresh install or using Norton Ghost, Casper 6 or Acronis True Image, the results are the same (BSOD).
It seems to me that either the drivers are wrong or a firmware update is need. I’ve contacted RunCore, but so far no good answer. The funny thing is, I tried this SSD (via and IDE/USB cable) on my MacBook Pro (using Super Duper) and it works just fine.
Have you any suggestions?
Thanks,
Bernie
It’s likely that your aging
It’s likely that your aging Sony lacks the necessary compatibility to handle the RunCore SSD – or vice versa.
@Bernie
IDE SSDs are rare,
@Bernie
IDE SSDs are rare, slow, and expensive for the size/performance you get. Adding an IDE SSD to an old laptop is not a good idea because Windows XP does not support SSDs as well as Windows 7 and new operating systesms, and the value of the SSD is likely to be higher than the old IDE device you are installing it in. If you have a system that only takes IDE drives, then your first priority should be to update to a SATA based laptop or new motherboard/CPU for a desktop. You can then later add a SATA based SSD to the system to increase performance.
Even if your SONY PCG-V505DC1 could take a SATA SSD, it will suffer from other bottle necks that would diminish the value and advantage that an SSD would provide.
It would be nice if you could
It would be nice if you could remind us which of these tests use random data, so we can tell how much of the difference is due to compression by the Sandforce controller that won’t apply to previously compressed files.
Any reason server operators shouldn’t expect expect longer life (more write cycles) from 32nm than 25nm? Performance is not the only criterion.
Doesn’t the Pyro only get 60k
Doesn’t the Pyro only get 60k iops, and it’s the Pyro SE that gets 85k iops isn’t it? Great review, been looking at the different Pyro’s for my first SSD, might bite the bullet one day!