Comment 14 for bug 461992

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Patrick Regan wrote:
> On 12/9/09, John A Meinel <email address hidden> wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Andrew Bennetts wrote:
>>> John: how much does the repo format matter to memory consumption? Given
>>> that the report started with bzr 1.14 I'm guessing this repo isn't using
>>> the latest format. (Although 1.1G is a pretty big repo even in 1.9 or
>>> pack-0.92 formats.)
>>>
>>> Also, does this bug need to be Critical? I don't think we'd block a
>>> release on fixing this (although obviously it would be great to fix or
>>> at least improve this).
>>>
>> I didn't mark it Critical, Patrick Regan did. I agree with the High
>> setting. I think Patrick was responding to Jim's comment that it
>> prevents them from using bzr.
>>
>
> That was indeed what I was responding to. I should have tried to read
> it more carefully and got more information before I marked it as such.
> My apologies.
>
> Pat
>

Just to clarify. Critical is "this must be fixed before we can release
the next bzr". It is reserved mostly for things which are regressions.
eg. if memory consumption tripled versus a previous bzr, then we would
consider that a regression that must be fixed.

This is fairly serious, but it may "already" be solved by upgrading to
the latest bzr with the latest repository format. (Though you probably
won't be able to do the upgrade with a 700MB VM.)

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAksf8uMACgkQJdeBCYSNAAMfKACgmjzB/2lBQNUCVdc6IfO0SYdN
Q/UAn25UocWMiQ2PhIBWFhxVP+miWssv
=bv3O
-----END PGP SIGNATURE-----