Work flow on large repositories

[Michael Hope]

Thank you for all of your comments.  I'll keep an eye on things over
the next few days and record a bit more (-Dmemory is quite
interesting) and see how things go.  There's a few comments inline
below...


On Thu, Jul 29, 2010 at 8:17 AM, John Arbash Meinel
<john at arbash-meinel.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>> Day-to-day work is done on topic branches.  Creating the branch takes
>> 46 s, 250 MB of RAM, and creates a 20 MB .bzr directory.  Pushing this
>> branch to LP for merging involves pushing the full 20 MB, but this is
>> acceptable.
>
> I can't say I fully understand this. Testing it here:
>  $ time bzr branch trunk test -Dmemory
>  PeakWorking          25824 KiB
>  real    0m0.974s
>  $ du -ksh test/.bzr/
>  265K    test/.bzr/

michaelh at crucis:~/c/gcc/gcc-linaro$ time bzr branch 4.4 test -Dmemory
Branched 93541 revision(s).
VmPeak:   267768 kB

real    3m49.509s
user    0m47.875s
sys     0m11.833s

michaelh at crucis:~/c/gcc/gcc-linaro$ du -sk test/.bzr/
20352   test/.bzr/

>> Doing a bzr pull on the 4.4 mirror directory may more than half an
>> hour and more than 500 MB of memory.
>
> Is that with the mirror already up to date? To branch all of
> lp:gcc-linaro took me about 65minutes. To add 4.4 to it took 8.5min and
> 52MB of content transfer.

A mix.  If there's nothing to pull then things are fast.  I was on the
4.4 branch under a mirror branch, did a bzr pull, and waited.  The
branch isn't very active so it shouldn't have had much to do.

-- Michael