"bzr push" transfering 15MB to commit a 400-lines patch?

[John Arbash Meinel]

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

Stefan Monnier wrote:
> I recently started to pay more attention to that transfer size info
> displayed during transfers and noticed that sometimes a lot more data
> gets transfered than what I'd expect.  E.g. I just pushed (actually
> via "commit" on a bound branch) a 400-lines patch (to 5 files totalling
> a max of 200kB) and Bzr told me it transfered more than 14MB of data
> for that.  This was using a "bzr+ssh" transport with a "bzr.dev" at most
> one month old.
> 
> Is that expected?  Is it a known problem?
> 
> 
>         Stefan
> 
> 
> 

Is that bzr.dev on both sides? If the remote side didn't support
autopack as an RPC, then it is certainly possible. As we then have to
download the contents of the files to pack, and then upload it again.
(So your 14MB is actually 7MB going both ways).

If your server *does* support autopacking, then that is pretty surprising.

John
=:->

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

iEYEARECAAYFAknBz9wACgkQJdeBCYSNAANSOgCcDCe9amy5/RqMHSV7t1QAe7Mv
KW4AoNGHRbSkPnlLzNS0FcMXj5W5ka4I
=EceH
-----END PGP SIGNATURE-----