Recommendations on compacting revision history.

[John Murtari]

Rob,
>> Folks,
>>
>> Have a web site project with about 1800 files.  Love bzr and it has
>> made management easy.   We notice that it seems to be slowing down
>> a bit when we do commits/updates.
>>
>> Right now we are up to revision 400.     We really don't care about a lot
> There shouldn't be any noticable slowdown after 400 revisions; bzr
> doesn't read all of history on commands like commit or update.
>
> That said, there is an amortised maintenance task that happens on
> power of 10 revisions, with power of 10 work at each occurence: so the
> 400th commit will be compacting the last 100 commits into a single
> data structure; the 1000th will be compacting the last 1000 commits,
> etc.
>
> bzr.log may shed some light as to whether this is what you are noticing.
>
> -Rob

         Okay, thanks for that info.   I thought there had to be some 
automatic
compaction going on inside.  Thanks again!

-- 
                                                John
________________________________________________________________
Customer Service                        Software Workshop Inc.
jmurtari at thebook.com                   "software that fits!" (TM)
(315) 944-0999 (x-211)                    http://www.thebook.com/
                                                                                                            `