On Thu, Apr 27, 2006 at 11:28:27AM +0200, Koen Kooi wrote: > Pulling the monotone repo could have been nearly twice as fast, since > almost half of the revisions are merges. 'commit before update' is > great, but PR wise you are shooting yourselves in the foot IMO.
Well, maybe. We _should_ be fast enough that it doesn't matter, though :-). (We also could make the initial pull go at line speed trivially, if we wanted; just feed the raw data straight out of the db and straight into the other side's db. It's just that we're still trying to see how far we can get with "safe" before we give it up.) Also, data point: in the monotone repo, only ~1/5 of the revisions are merges. (Presumably this varies with a group's habits.) Getting rid of 1/5 of the revisions probably would make things somewhat faster, it's true... in monotone's case, it was only a few months ago that we _had_ 4/5 as many revisions as we do now. Using a pull of net.venge.monotone is slightly problematic as a benchmark, because the benchmark data set has been growing larger almost as fast as we've been optimizing :-). -- Nathaniel -- "If you can explain how you do something, then you're very very bad at it." -- John Hopfield _______________________________________________ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
