some timings using bzr

[Robert Collins]

On Fri, Jul 11, 2008 at 9:12 PM, David Ingamells
<david.ingamells at mapscape.eu> wrote:
> Robert Collins wrote:
>>
>> Using bzr:// locally means you have twice the overhead - you have bzr
>> running twice and processing data twice. So I'd expect it to be
>> slower. When you have two machines each gets to share the load.
>>
>>
>
> This was on a machine with 2 dual core CPU's...
> Admittedly only one socket...
>

interesting. Its also possible that the network stack on the machine
had some timing condition. Oh! There was a bug in bzr a release or so
back that made local network terribly slow with some versions of the
linux kernel; I'll bet that that is what it was.