[RFC] remove rspush?

[John Arbash Meinel]

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

Jelmer Vernooij wrote:
> Am Freitag, den 05.10.2007, 12:24 -0400 schrieb Aaron Bentley:
>> The bzrtools rspush command was essential in the days when we didn't
>> have integrated push support, but these days, it seems redundant.  I
>> haven't used it in at least a year.
>>
>> Worse yet, it's out of date.  It doesn't know how to deal with anything
>> except standalone trees, and doesn't even work with working tree format 4.
>>
>> And no one has noticed that it was broken 'till recently.  So I think
>> it's time to retire it.  Any objections?
> I know some of the other Samba developers are using it heavily for one
> of their projects, where pushing trees within a sane amount of time is
> impossible without rspush. I think they're still on an older version of
> bzr and bzrtools, but I think it will still be very valuable until packs
> land. Personally, I still use rsync for initial push although I just
> invoke the command directly.
> 
> Cheers,
> 
> Jelmer

- From my testing, rsync has only been faster for initial push for a long time.
For incremental updates, knits have been faster (and safer) since:
  http://bazaar-vcs.org/Performance/0.11

And with Andrew's streaming api, it should be:

a) faster still for incremental
b) approximately the same speed as rsync, since it gets to send everything in a
big stream.

Actually, probably the fastest (network-wise) would be to un-gzip the hunks,
and bzip2 the stream, and have them recompressed on the other side. But that
does cost a bit of cpu power. Sending gzip hunks is probably a reasonable tradeoff.

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHB7L/JdeBCYSNAAMRApTDAKDFFhsWvunRCPHjTSNeWCjGE3HETQCdF2Jz
XgAOjQzdXf7l1EwU6hGqsuc=
=Hu8g
-----END PGP SIGNATURE-----