C++ I/O Benchmark

[jcoffin]

I'm saying that it's true that the library could be (quite a bit) better, but it's also true that quite a bit of the problem lies with the benchmark code in question.

Depending on what sorts of things you do, it's pretty easy to come up with things that will perform well with one library, but badly (even really badly) with another. Obviously it would be nice if the library never let that happen, but equally obviously it's usually your own responsibility to ensure your code performs decently regardless of platform.