AkG
Well-known member
- Joined
- Oct 24, 2007
- Messages
- 5,270
IOMETER / IOMeter Stutter Test
IOMeter is heavily weighted towards the server end of things, and since we here at HWC are more End User centric we will be setting and judging the results of IOMeter a little bit differently than most. To test each drive we ran 5 test runs per HDD (1,4,16,64,128 que depth) each test having 8 parts, each part lasting 10 min w/ an additional 20 second ramp up. The 8 subparts were set to run 100% random, 80% read 20% write; testing 512b, 1k, 2k,4k,8k,16k,32k,64k size chunks of data. When each test is finished IOMeter spits out a report, in that reports each of the 8 subtests are given a score in I/Os per second. We then take these 8 numbers add them together and divide by 8. This gives us an average score for that particular queue depth that is heavily weighted for single user environments.
This flattening of the performance line with no fall off at the end really highlights how hobbled the controller in this solid state drive is. Instead of being able to do as good as it can and peak like darn near every other newer generation SSD (which isn’t being limited by something or having its numbers artificially boosted by massive cache) we have reviewed, the Kingston SSDNow is hitting an artificial wall induced by the fact that this 10 channel beast of a controller is only operating in 5 channel mode. While in this degraded state it is obvious that it can more than easily meet darn near any demands IO Meter can throw at it and is only limited by the number of chips it can access.
The other thing which is blatantly obvious is that a mere $120 drive just beat the pants off of much more expensive drives….including an SLC-based one (Agility EX)! To be honest none of this is unexpected and IOMeter really hasn’t shed any new light on the potential of the SSD Now V seriess.
In our usual IOMeter test we are trying to replicate real world use where reads severly outnumber writes. However, to get a good handle on how well a Solid State Disk Drive will handle a worse case scenario (and thus how likely the dreaded stutter issue will happen) we have also run an additional test. This test is made of 1 section at que depth of 1. In this test we ran 100% random. 100%writes of 4k size chunks of information. In the .csv file we then found the Maximum Write Response Time. This in ms is worst example of how long a given operation took to complete. We consider anything higher than 333ms (one third of a second) to be a good indicator that stuttering may happen, with the higher the number the worse the duration of the stutter will most likely be.
Honestly an average number of 0.13 is very impressive and even the Kingston drive's maximum number of nearly 386 is good. What this means is that even in worst of scenarios, this drive shouldn’t stutter. A little more than a third of a second is about the most we would want to see in any Solid State Drive we would considering purchasing, but chances are very slim that you will ever notice any stuttering with this particular drive (at least we didn’t while using it).
IOMeter
IOMeter is heavily weighted towards the server end of things, and since we here at HWC are more End User centric we will be setting and judging the results of IOMeter a little bit differently than most. To test each drive we ran 5 test runs per HDD (1,4,16,64,128 que depth) each test having 8 parts, each part lasting 10 min w/ an additional 20 second ramp up. The 8 subparts were set to run 100% random, 80% read 20% write; testing 512b, 1k, 2k,4k,8k,16k,32k,64k size chunks of data. When each test is finished IOMeter spits out a report, in that reports each of the 8 subtests are given a score in I/Os per second. We then take these 8 numbers add them together and divide by 8. This gives us an average score for that particular queue depth that is heavily weighted for single user environments.
<img src="http://images.hardwarecanucks.com/image/akg/Storage/SSDNow/IOM.jpg" border="0" alt="" />
This flattening of the performance line with no fall off at the end really highlights how hobbled the controller in this solid state drive is. Instead of being able to do as good as it can and peak like darn near every other newer generation SSD (which isn’t being limited by something or having its numbers artificially boosted by massive cache) we have reviewed, the Kingston SSDNow is hitting an artificial wall induced by the fact that this 10 channel beast of a controller is only operating in 5 channel mode. While in this degraded state it is obvious that it can more than easily meet darn near any demands IO Meter can throw at it and is only limited by the number of chips it can access.
The other thing which is blatantly obvious is that a mere $120 drive just beat the pants off of much more expensive drives….including an SLC-based one (Agility EX)! To be honest none of this is unexpected and IOMeter really hasn’t shed any new light on the potential of the SSD Now V seriess.
IOMeter Stutter Test
In our usual IOMeter test we are trying to replicate real world use where reads severly outnumber writes. However, to get a good handle on how well a Solid State Disk Drive will handle a worse case scenario (and thus how likely the dreaded stutter issue will happen) we have also run an additional test. This test is made of 1 section at que depth of 1. In this test we ran 100% random. 100%writes of 4k size chunks of information. In the .csv file we then found the Maximum Write Response Time. This in ms is worst example of how long a given operation took to complete. We consider anything higher than 333ms (one third of a second) to be a good indicator that stuttering may happen, with the higher the number the worse the duration of the stutter will most likely be.
<img src="http://images.hardwarecanucks.com/image/akg/Storage/SSDNow/stutter.jpg" border="0" alt="" />
Honestly an average number of 0.13 is very impressive and even the Kingston drive's maximum number of nearly 386 is good. What this means is that even in worst of scenarios, this drive shouldn’t stutter. A little more than a third of a second is about the most we would want to see in any Solid State Drive we would considering purchasing, but chances are very slim that you will ever notice any stuttering with this particular drive (at least we didn’t while using it).
Last edited by a moderator: