2.0 upgrade experiences

[Robert Collins]

obsolete_packs is cleaned up just-before the next autopack operation.

Doing it after every commit would be a) expensive and b) more likely to
run into trouble during batch scripts and fragile fs's.

autopack operations occur every 10 or so commits. 

I you have (say) 12345 commits in your repo, then the number of
permitted packs is 1 + 2 + 3 + 4 + 5 = 15. So doing
bzr pack
gives you one pack.
And doing 5 more commits will drop your permitted pack count to 
1 + 2 + 3 + 5 + 0 = 11, with 6 packs in the repo
The next 9 commits will take you to a limit of 20, with 15 packs in the
repository.
And one more commit will take you to a limit of 12 (1 + 2 + 3 + 6 + 0),
with 16 packs in the repository, triggering an autopack of the 5
smallest packs.

Every 10 after that will autopack 10 packs, for the next 30 (when you
pass another power of ten - 1 + 2 + 4 + 0 + 0), and it will pack down to
7 packs (packing 12 packs). Then every 10 packing 10 packs, for 99
commits, the hundredth packing 20 packs, and so on.

-Rob

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20090908/df31e885/attachment-0002.pgp