[darcs-users] Benchmarking "get"

zooko zooko at zooko.com
Tue Mar 17 20:49:52 UTC 2009

Lele Gaifax converted the Tahoe repo [1] from darcs (hashed-format)  
to git and reported the following times for "darcs get" and "git  
clone" on a local filesystem:

$ time git clone $a
Initialized empty Git repository in /tmp/w/git-side/.git/

real    0m27.486s
user    0m0.088s
sys     0m0.964s

$ time darcs get /tmp/testtahoe/rootdir/darcs-side
Copying patches, to get lazy repository hit ctrl-C...
Finished getting.

real    0m24.188s
user    0m21.857s
sys     0m1.924s

Hey, that's weird, why is user+sys << real for git?

He also reported the sizes of the repositories:

$ du -sb git-side
76990124        git-side

$ du -sb darcs-side/
57285206        darcs-side/

Subjectively, I don't have a problem with the performance of "darcs  
get".  I do have a problem with command-lines like these:

darcs query contents --quiet --match "hash  


darcs annotate --xml-output --match "hash 20081124204046-e01fd- 
b4d82d92f5fc8d9af65af44ccce8c29279fb73af.gz" src/allmydata/interfaces.py

Whenever you hit this URL: http://allmydata.org/trac/tahoe/browser  
trac issues commands like those to darcs, and currently it can often  
take tens of seconds for darcs to generate the answer, which causes  
trac to time-out and return an error to the user.


Tahoe, the Least-Authority Filesystem -- http://allmydata.org
store your data: $10/month -- http://allmydata.com/?tracking=zsig

More information about the darcs-users mailing list