On Thu, Jan 14, 2010 at 06:31:04 -0800, Jason Dagit wrote: > || darcs | darcs-2.3.1 > ================++===============+=================== > check || 41.1s 253.0M | 11.0s 55.0M > repair || 40.7s 247.0M | 11.0s 55.0M > === ghc-hashed === > > || darcs | darcs-2.3.1 > ================++================+=================== > check || - - | 186.2s 142.0M > repair || 1223.2s 370.0M | 130.6s 146.0M
> Looks like repair has gotten much worse :( Check didn't complete? I'll note that Kevin Quick posted a bug report about a noticeable Darcs 2.3.x having a performance regression wrt 2.2.x in check/repair/whatsnew http://bugs.darcs.net/issue1678 Do I understand correctly that it's just gotten even worse? Do you think you could also add a darcs-2.2 to that mix? I guess we can't really worry about this for the Darcs 2.4 release; we have to focus on hitting the repo-local operations. -- Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow> PGP Key ID: 08AC04F9
signature.asc
Description: Digital signature
_______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
