I appreciate the timings! It looks like darcs 2.3 + hashed comes out ahead (having glanced at them, sorry if I drew the wrong conclusions)
> The solution seems to be to switch to darcs 1 hashed format locally. I > note that darcs-2.3 now defaults to the hashed format when getting a new > repo. However we get no advice about existing repos and get hit with up > to a 100x slowdown. We have you to thank for http://bugs.darcs.net/issue1583 > So, it would be nice if we got told that we should switch, and if there > were a more convenient way of doing it. By convenient I mean inplace > without affecting my working copy. I've got 100's of local darcs repos > and it'll be a pain to switch them all and preserve all the unrecorded > changes. and for http://bugs.darcs.net/issue1584, both ProbablyEasy bugs which I think it would be nice to rope some Hack Day participants into fixing. Perhaps during the Hack Day, I'll have a moment to play with Petr's darcs-benchmark (cabal install darcs-benchmark is just about all it takes, if I understand correctly) -- Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow> PGP Key ID: 08AC04F9
pgpfLcoOThFbP.pgp
Description: PGP signature
_______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
