On Thursday, May 24, 2012 at 11:05 AM, Josh Durgin wrote: > Why not have the read benchmark write data itself, and then benchmark > reading? Then both read and write benchmarks can clean up after > themselves. > > It's a bit odd to have the read benchmark depend on you running a write > benchmark first. > > Josh We've talked about that and decided we didn't like it. I think it was about being able to repeat large read benchmarks without having to wait for all the data to get written out first, and also (although this was never implemented) being able to implement random read benchmarks and things in ways that allowed you to make the cache cold first. Which is not to say that changing it is a bad idea; I could be talked into that or somebody else could do it. :) -Greg -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
