bzr branch is slow and memory-hungry (just a data point)

[Michael Alan Dorman]

I'm really not expecting things to be heavily optimized at this
juncture, but I thought I would report on my experiences with 'bzr
branch' on a non-trivial project tree I recently converted from cvs
(where it's got a couple of years worth of history) using tailor.

'bzr info' on the tree reports:

  branch format: Bazaar-NG branch, format 0.0.4

  in the working tree:
         986 unchanged
           0 modified
           0 added
           0 removed
           0 renamed
           0 unknown
         237 ignored
         236 versioned subdirectories

  branch history:
        3148 revisions
           1 committer
           0 days old
     first revision: Tue 2005-09-06 13:48:52 -0400
    latest revision: Tue 2005-09-06 18:34:49 -0400

  text store:
        7845 file texts
       24512 kB

  revision store:
        3148 revisions
        1161 kB

  inventory store:
        3148 inventories
      129152 kB

The branch process takes 4.5 minutes, during which the bzr process
dominates the CPU (not that there's any competition on my laptop) and
balloons to 425MB.

I must say, though, I've been looking at bzr for projects that are
currently using both bazaar and cvs, and it generally looks good in
both situations.

Mike