Large repo & filtered views

[Ian Clatworthy]

Krzysztof Nowicki wrote:
> Hi,
> 
> I've been experimenting with migrating a large repository to Bazaar. It's size
> is ~7GB (3GB compressed with 2a), ~25000 files. The repository was created
> without problems (maybe except of memory consumption - we have some large
> binaries in the repo). However I realized that using such a repo will be real
> pain, as for every branch I'll need at least 7GB of space.

Make sure you're using a shared repository so all storage is in the one
place. Then each branch only effectively takes the size of your working
tree. If that's too large, you can use one working tree and share it
across branches - see 'reusing a checkout' in the User Guide.

> Immediately I thought about filtered views and had hope that it would allow me
> to checkout only a subset of files and save some space. Unfortunately they don't
> seem to work the way I imagined, because a view only filters the status
> information presented in the UI, whereas the underlying storage is unchanged
> (i.e. the working tree still contains all files).

That's right. Also be aware that filtered views are currently an
"experimental" feature. I say that because they have only recently been
added and haven't been tested a lot.

> Is there a plan to support checking out only a subset of files? I'd imagine that
> nested trees would be the perfect solution, but is such a feature also planned
> for the existing filtered views?

Yes. No promises on timeframe though.

Ian C.