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

[Robert Collins]

On Thu, 2009-03-19 at 00:32 -0400, 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?

Both expected and fixed if you upgrade your server. Heres whats
happening:
There is a bunch of overhead in doing lots of bzr:// operations, (beyond
latency :P).
bzr 1.13 will not use the highly optimised but VFS-layer pack-to-pack
copying if it thinks your server might support the 1.13 streaming
approach which is superior - no remote index reads, remote autopack etc.

So - if you were running 1.12 on the server, you'd get the pack-to-pack
copying. If you were running 1.13 (or newer) on the server you'd get
new-format streaming. Running bzr.dev from ~ a month ago you get the
worst of all worlds :(

-Rob
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20090319/7e2b61c8/attachment.pgp