Comment 8 for bug 137449

I note that just before doing the add/status part of the benchmark, it's done a non-repository branch of all the trees, which is going to read 300MB of repository data, write out 300MB of repository data, plus building a 300MB tree. That's 2700MB of data in transit in total altogether, so we're likely to still be under memory pressure when we start the next operation. I'm speculating that by the time we start the next one, we'll have more clean buffer pages.

I think we really need to change usertest to do all the operations on the first tool, then everything on the second, and so on. Then the memory and buffer usage generated by any run of bzr will mostly penalize its own operations. I'm not sure how to account for the followon cost from one to the next; possibly running 'sync' and waiting for a while.