Howdy, Stranger!

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

Sign In with Google


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:

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,

Write performance question

edited July 2011 in DrivePool

I know performance tuning probably isn't a high priority right now, but are you guys planning on focusing on that at some point?

I tested copying a file first to a non pooled drive... I was getting aproximately 110 MB/s during the write.

Copying the same file to a pooled drive dropped to about 45 MB/s.

Is there room for performance improvements, or is this pretty much what we can expect in the final release (due to the way it works under the hood)?

I have't played around with read speeds yet... I'm hoping read speeds aren't impacted by pooling.



  • Covecube
    From the beginning, DrivePool was engineered to support a performance layer. This means that we can approach that 110 MB/s. It's not there now, but theoretically no old code has to be rewritten (perhaps maybe a bit), only new code has to be written to make it fly.

    So the answer is yes, read / write speed is not optimal right now, and we can definitely make it go faster. Hopefully, much faster.

    This performance layer will be added in BETA M4.
Sign In or Register to comment.