Deploying with Bazaar (or how a big repo can make you crazy)

Leonardo Santagada santagada at
Fri Mar 9 12:02:05 UTC 2012

On Fri, Mar 9, 2012 at 7:39 AM, Eli Zaretskii <eliz at> wrote:
>> Date: Thu, 08 Mar 2012 19:09:09 +0100
>> From: Jelmer Vernooij <jelmer at>
>> Cc: Bazaar users <bazaar at>
>> SSH by itself isn't any faster, but the fact that you're running the bzr
>> smart server protocol over SSH. The smart server protocol (HPSS) is
>> optimized for bzr operations. If you use a "dumb" transport, like plain
>> HTTP, FTP or SFTP then you're basically reading the raw remote files and
>> fetching whatever bits you need by parsing them. This can involve
>> loading a (part of) a large pack file into memory. With the smart server
>> protocol, your client can just ask for specific data.
> But in the initial "bzr branch" command, the smart server doesn't
> help, does it?  Because it needs to fetch all the history anyway,
> right?
> At least this is what was explained to me in this thread:

Yes, and what is worse, I had configured a shared repo, so maybe that
is part of the culprit for the memory craziness even when using a
smart server. I thought a shared repo could only help, and also that
bzr would be saving something there even during fetch.


Leonardo Santagada

More information about the bazaar mailing list