Comment 14 for bug 736001

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

On 03/22/2011 10:48 AM, Julian Edwards wrote:
> On Tuesday 22 March 2011 09:16:05 you wrote:
>> I think making it configurable would be ok. The furthest I would
>> probably go at this point is to give a way to disable automatic
>> repacking, for users who promise to make other arrangements to repack
>> from time to time.
>
> It might be worth adding instructions for the (new) config in the output when
> you start doing the auto-packing. That way the user can immediately see a way
> to avoid the lengthy repack if they're in a hurry.
>

Note that my Launchpad repository *just* rolled over 100k revisions,
which is the "really really big and long" repack. That is partially
because it also includes the dependencies as part of one-big-repository.

However, that means that +/- a couple months people working with
Launchpad are going to be hitting a big repack. In my case it took 13
minutes, which is certainly invasive. (Happened to be at a time that I
wanted to 'move quickly', too.)

100k inventories, 550k chk pages, and 369k file texts do take a while to
repack.

I wonder if we want to just have a maximum-auto-repack setting, with a
default of something like 10k revisions. And a possible warning if we
think we should repack more than that.

We might consider even defaulting to more like 1k revisions.

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

iEYEARECAAYFAk2MlQsACgkQJdeBCYSNAAOfbgCeNx45yyQjp/8Y9UJxSvX0Eyc2
5LkAoNhIrh9Rx91As8XDqmI/MYvak/d5
=YZYl
-----END PGP SIGNATURE-----