Bazaar NG performance on large repositories

[Nicholas Allen]

>
> ^- How many working files? 20K revisions doesn't seem like too many, but
> because of a bug like:
> https://launchpad.net/products/bzr/+bug/68512
>
> If you have a huge tree, we store too many full copies of the inventory
> text. The data format doesn't care, so we could simply change the
> creation code to save some space here. (Just to say, we can fix this in
> a completely compatible way).
>   
There are 5270 files and 343 directories.
>
> ^- I'm a little surprised that it takes that long to create the working
> tree, but yes, it is something that needs to be optimized.
>   
It's useable in its current state because a branch is not something that 
we would do that often. But it would be nice if it was sub 1 minute.
>   
> There is a *huge* room for improvement, related to stuff like:
> https://features.launchpad.net/products/bzr/+spec/per-file-log-output
>
> Basically, we already store a graph of what revisions have modified the
> file. At present, we are using old code which looks at the global graph,
> and then extracts each version to see if the file was modified. It is
> very sub-optimal, but we have all the data available to make it very
> fast. We just need to start using it.
>
>   
That's good to know ;-)
>
> Were you pushing over sftp, or to another branch on your working
> machine? (Or to bzr+ssh:// on another machine?)
>   

I was pushing to a local branch on my working machine.