On Fri, 2009-12-11 at 00:10 +0000, Ernst wrote:
>
> I read somewhere bzr is more optimized for round trips than for data
> bandwidth; it assumes a lot of bandwidth is available, and thus
> latency
> is the limiting factor (I don't know if this is true and if it still
> holds for 2a).
It's never been the case. bzr tries to use a little data and as few
round trips as possible, but there is a relationship between them.
packing occasionally is necessary to prevent a data * latency multiplier
effect occuring over time; it doesn't happen on every commit, and if
you're working with 3G, turning it off would be a very bad idea.
In short:
- use a smart server (will pack for you)
- or performance will get linearly worse, at approximately 5 * your RTT
per commit.
On Fri, 2009-12-11 at 00:10 +0000, Ernst wrote:
>
> I read somewhere bzr is more optimized for round trips than for data
> bandwidth; it assumes a lot of bandwidth is available, and thus
> latency
> is the limiting factor (I don't know if this is true and if it still
> holds for 2a).
It's never been the case. bzr tries to use a little data and as few
round trips as possible, but there is a relationship between them.
packing occasionally is necessary to prevent a data * latency multiplier
effect occuring over time; it doesn't happen on every commit, and if
you're working with 3G, turning it off would be a very bad idea.
In short:
- use a smart server (will pack for you)
- or performance will get linearly worse, at approximately 5 * your RTT
per commit.
-Rob