Hi Zooko, I've got a few questions:
1. Am I correct that all these timings involve push -a and pull -a when there is nothing to push or pull? (That's That's definitely an interesting case, but I'm worried by it taking 12-17s to report there are no patches to push/pull. 2. Did you enable a global cache directory with ~/.darcs/sources as described in http://wiki.darcs.net/index.html/DarcsTwo (search for global cache) 3. Did you repeat your measurements? In particular, if you use a global cache the second time you push/pull with either --hashed on both sides or --darcs-2 on both sides should be lightning fast. (And if it's not, I want to figure out why.) I think that's all the questions I've got just now. David On Tue, Jan 22, 2008 at 10:02:35PM -0700, zooko wrote: > Folks: > > I just made a quick measurement of darcs-2 performance. > > Using darcs 1.0.9 I can do "push -a" to another repo which is > connected by 802.11g (and which has all the same patches as the > source repo) in 3.5 s (all measurements are best of four trials), and > can do a "pull -a" in 12.7 s. > > Using darcs 2 with this repo in hashed format and the remote repo in > old format, push takes 0.15 s and pull takes 0.16 s. > > Using darcs 2 with this repo and the remote repo in darcs-2 format, > push takes 10.7 s and pull takes 17.0 s! > > > So as far as pushing and pulling when both repos have the same set of > patches, using hashed format is much faster than using darcs-2 format! > > > The repo in question is publically available (and chock full of very > cool source code that you are welcome to use): > > http://allmydata.org/source/tahoe/trunk > > Regards, > > Zooko > > _______________________________________________ > darcs-devel mailing list > darcs-devel@darcs.net > http://lists.osuosl.org/mailman/listinfo/darcs-devel -- David Roundy Department of Physics Oregon State University _______________________________________________ darcs-devel mailing list darcs-devel@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-devel