Comment 8 for bug 408531

If this is specifically about large-memory consumption during "bzr branch", this has, indeed, been addressed in bzr-2.1.0b2 (and thus b3 as well).

*A* problem with a bug like "require lots of memory" is that there isn't a clear point when the bug can be considered closed. The old code didn't really grow without bounds, it just had a high bound (say 1GB to branch a Launchpad branch), and the new code has a lower bound (approx 512MB now).

That doesn't let us do the work in say 128MB, but it is *better*. It is a bit hard to give an explicit memory bound for an operation. Lower is always better, but I certainly think that if you are doing an operation on a large amount of data, it is reasonable to expect it to consume more resources (memory, cpu time, etc.)

I don't think there are many remaining "easy-to-trim" memory consumption changes to be made at this point. I'm sure more could be done, but we are certainly into the "effort-vs-benefit" level.

I'm tempted to mark this as fix released in bzr-2.1.0b2 and open a new bug if we want to continue the discussion.