Here's a bit of preliminary timing to show you the difference. Note that these times have several inaccuracies and should only be used as an extremely general indication of speed. A few caveats that I know of:
Baseline rsync This runs rsync and then does a lightweight checkout in the directory (leaving us with a branch and working tree just like a bzr branch operation.)
rsync -a rsync://bzr.fedorahosted.org/bzr/packagedb/ . cd fedora-packagedb-devel bzr checkout --lightweight
real 0m16.548s
bzr over http This is equivalent to what we have had to use on the old server:
bzr branch
http://bzr.fedorahosted.org/bzr/packagedb/fedora-packagedb-devel
Branched 258 revision(s).
real 1m2.844s
Ouch!
A fresh branch using the smart server
bzr branch bzr://bzr.fedorahosted.org/bzr/packagedb/fedora-packagedb-devel Copying repository content as tarball... Branched 258 revision(s).Much better! This is only 7 seconds slower than using rsync.
real 0m23.192s
bzr+ssh smart server for rw access:
bzr branch bzr+ssh://bzr.fedorahosted.org/bzr/packagedb/fedora-packagedb-devel Copying repository content as tarball... Branched 258 revision(s).The ssh protocol adds a few seconds to the total time but it's also quite speedy.
real 0m25.501s
One interesting point is that the smart server times are much better than the ones I posted in October. This could be because we're dealing with a different server on a different network or it could be that we've gone from using bazaar-0.18 to bazaar-1.0rc3 on the server. I'll have to do more timings after we get settled into the new machine to tell more.
FOAF updates: Trust rankings are now exported, making the data available to other users and websites. An external FOAF URI has been added, allowing users to link to an additional FOAF file.
Keep up with the latest Advogato features by reading the Advogato status blog.
If you're a C programmer with some spare time, take a look at the mod_virgule project page and help us with one of the tasks on the ToDo list!