Comment 3 for bug 404047

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ernst wrote:
> Well, it seemed bzr-gtk was causing some troubles. Still, bzr update is very, very slow (it is running for more than 20 minutes, I think). See the log file. Is this caused by the new format 2a? The repository is accesed over a ftp connection, that could be related?
> For sure, with the 1.14 format the update was much, much faster.
>
> ** Attachment added: "bzrlog2.txt"
> http://launchpadlibrarian.net/29488667/bzrlog2.txt
>

So it is 100% related to the fact that we are going over FTP, which doesn't
allow us to do a "partial download". So instead every time we need XX bytes
from the file, we download the whole content, extract those bytes and then
throw it away.

Potentially our FTP layer could be taught how to do some caching, and this
would probably improve dramatically. The main issue is how do you decide on a
lifetime for the cache, do you cache in memory or on disk, or ....

If you used bzr+ssh or sftp or http your results would most likely be
dramatically better.

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFKaf9ZJdeBCYSNAAMRAu1nAKCqyMsyoTZWFXXw49udvPCwGL5/lQCgtPpA
yNW4EdmI/i+qRt6t4qljbhY=
=ntnM
-----END PGP SIGNATURE-----