Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In with Google

Our Sites

covecube.com 
community.covecube.com 
blog.covecube.com 
wiki.covecube.com 
bitflock.com 
stablebit.com 

Poll

No poll attached to this discussion.

In order to better support our growing community we've set up a new more powerful forum.


The new forum is at: http://community.covecube.com


The new forum is running IP.Board and will be our primary forum from now on.


This forum is being retired, but will remain online indefinitely in order to preserve its contents. This forum is now read only.


Thank you,

M4 read performance

edited January 2012 in DrivePool
I was curious on the M4 read performance so I did a quick benchmark to try to find out if this read-striping works. I made a small tool that reads a 4 GB file using unbuffered read (bypassing Windows file cache).

Reading duplicated file from pool using read-striping:
Read 4771020800 bytes, elapsed time 00:00:40.4042590, transfer speed 115314 Kbyte/s

Reading duplicated file from pool without read-striping:
Read 4771020800 bytes, elapsed time 00:00:40.2170578, transfer speed 115851 Kbyte/s

Reading the same file directly from the disk:
Read 4771020800 bytes, elapsed time 00:00:43.6802800, transfer speed 106665 Kbyte/s

The difference is neglect able and not something you'd notice in practice. The good thing is that reading from the pool is just as fast as from the native drive. Alex: How optimized is M4 when it comes to performance at this time?

As for write speed I've not tested since I use duplication and write speed will equal the time to write on the slowest drive used of the two.

Comments

  • Covecube
    Read striping may not double your read speed. It works well in limited BUS scenarios like USB 2.0. Still testing / tweaking  this feature to see if it's worth it.

    M4 read / write performance should be optimal.

    Opening many small files is not optimized at this time.
Sign In or Register to comment.