> But I'm not sure if it is exercising the sort of problem that I > have. The speed of "annotate" seems to have gotten dramatically > *worse* since darcs 2.3. I guess this means I shouldn't upgrade to > darcs 2.4!
It would be good if you could help us reproduce this (and maybe open a ticket). Here's what I get on the darcs darcs repo with Darcs 2.3.1, the current beta and an unstable version with some recent work. % darcs-benchmark run darcs-2.3.1 darcs-2.3.98.2 darcs-2.3.99.1p1 / darcs --only annotate +----------++--------------------+-----------------------+-------------------------+ | || darcs-2.3.1 | darcs-2.3.98.2 | darcs-2.3.99.1p1 | +==========++====================+=======================+=========================+ | annotate || 18.1s 181.0M | 16.5s 181.0M | 16.6s 181.0M | +----------++--------------------+-----------------------+-------------------------+ For the interested, darcs-benchmark is just a cabal install away. Setting it up for your favourite repo is pretty painless. Either just call it "repo.whatever", or write a config file "config.whatever" in the JSON format I mentioned earlier and attached again for convenience. darcs get --lazy http://code.haskell.org/darcs/darcs-benchmark -- Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow> PGP Key ID: 08AC04F9
{ "name" : "GHC"
, "path" : "repo.ghc-hashed"
, "annotate" : "HACKING"
}
pgp8drKZEP53g.pgp
Description: PGP signature
_______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
