A thread you want to click! Yes i love them too. 
Alright, so i ordered 5 Intel X25-V 40GB SSDs, put them in the server and created a RAID0. I don't have too much time at the moment, but i wanted to share my first benchmark:
This benchmark is testing with 4KiB - 128KiB request size; so average a little above 64KiB. You can calculate the MB/s by multiplying the average request size with the IOps score. So our calculation would be (<iops> * 64) / 1000 = MB/s:
1-queue = 240MB/s
2-queue = 430MB/s
4-queue = 684MB/s
16-queue = 1100MB/s
64-queue = 1233MB/s
128-queue = 1234MB/s
256-queue = 1236MB/s
As you can see, it scales up to 64-queue where the maximum throughput is already achieved. This is not even sequential read; this is random read over the entire 'surface'. Though with a high queue enough it is just as fast as sequential read. I will post 512-byte and 4K random read scores later. Probably will make a nice article with lots of benchmarks. The fun thing is; benchmarks take alot less time. That's also dangerous as the scores fluctuate more if it runs shorter.
Hope you guys like this teaser - more to come!
Alright, so i ordered 5 Intel X25-V 40GB SSDs, put them in the server and created a RAID0. I don't have too much time at the moment, but i wanted to share my first benchmark:
Code:
RAIDTEST on /dev/stripe/intelstripe - testing random read/write performance
concurrency performance in I/O's per sec. average
1 (read) 3691 3769 3794 3751
2 (read) 6702 6712 6709 6707
4 (read) 10716 10683 10667 10688
16 (read) 17173 17229 17206 17202
64 (read) 19274 19308 19260 19280
128 (read) 19262 19322 19302 19295
256 (read) 19312 19312 19335 19319
This benchmark is testing with 4KiB - 128KiB request size; so average a little above 64KiB. You can calculate the MB/s by multiplying the average request size with the IOps score. So our calculation would be (<iops> * 64) / 1000 = MB/s:
1-queue = 240MB/s
2-queue = 430MB/s
4-queue = 684MB/s
16-queue = 1100MB/s
64-queue = 1233MB/s
128-queue = 1234MB/s
256-queue = 1236MB/s
As you can see, it scales up to 64-queue where the maximum throughput is already achieved. This is not even sequential read; this is random read over the entire 'surface'. Though with a high queue enough it is just as fast as sequential read. I will post 512-byte and 4K random read scores later. Probably will make a nice article with lots of benchmarks. The fun thing is; benchmarks take alot less time. That's also dangerous as the scores fluctuate more if it runs shorter.
Hope you guys like this teaser - more to come!