Hi Zooko, We're painfully aware of the suffering that darcs annotate and show contents can cause.
On Fri, Feb 05, 2010 at 10:48:19 -0700, Zooko Wilcox-O'Hearn wrote: > darcs query contents --quiet --match "hash 20081109101536-c31ef- > ccf6657d1e8ed9208677f19bf620868c23da72e4.gz" > "src/Darcs/Hopefully.lhs" For the interested, here is the latest status on this bug: http://bugs.darcs.net/msg9192 (issue1447 update 2009-11). The bad news: I'm afraid our attention is focused on other performance issues right now. Petr has been squashing hashed-storage regressions (rah!). For Darcs 2.5 we have a few other issues closer to the front of the queue. The good news: We'll be seeing Benedikt Schmidt, author of the filecache optimisation at the Zurich hacking sprint. If we manage to polish off filecache for Darcs 2.5, you'll have a much more bearable darcs annotate and hopefully darcs show contents too. > This takes a long time. For the Tahoe-LAFS repository, it takes so > long that the web site times out and hackers start asking if we can > please switch to git. One short-term solution might to use a git mirror as a sort of cache for the website. > Please put a "darcs query" like this one (querying the contents of a > not-the-most-recent-version of the file) I did not manage to do this, but I've made a note of it in an experimental bugs-everywhere (*) tracker: http://code.haskell.org/darcs/darcs-benchmark/reports > and a darcs annotate like this one in the darcs benchmarks. I see that > there is already something named "darcs annotate" in the benchmark > results: Progress: I've extended darcs-benchmark for better darcs annotate support. The issue is that darcs-benchmark only looked for two candidate files to annotate, Setup.{hs,lhs}. See the attached example configuration file (in case you wanted to benchmark Tahoe-LAFS) darcs get --lazy http://code.haskell.org/darcs/darcs-benchmark In the darcs version of darcs-benchmark, you can now write an optional config file for each repo, telling darcs-benchmark which file to run darcs annotate on. One issue is that we're still not running darcs annotate on the GHC repo because it's so slow. Perhaps we could add a --thorough flag to darcs-benchmark to run some optional, excruciatingly slow, benchmarks. Meanwhile, you did say there was an annotate regression. I think it is important that we look into this before releasing Darcs 2.4. Eric (*) Bugs-everywhere lets us do distributed bug tracking backed by a darcs repo. One thing they support nicely is just shipping your bug db with your source code, so you could, eg. write the test (first), the bugfix, and then close the bug in the same patch. I thought it would be a good idea to try out for a small repository such as darcs-benchmark. Unfortunately, I have not had the time to look into setting up the interactive web UI or email interface; so it's read-only unless you're willing to install the command line tool http://bugseverywhere.org/be/show/HomePage -- Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow> PGP Key ID: 08AC04F9
{ "name" : "GHC"
, "path" : "repo.ghc-hashed"
, "annotate" : "HACKING"
}
pgpisek1qVNVx.pgp
Description: PGP signature
_______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
