[Chandler-dev] Compaction feature

[Andi Vajda]

On Thu, 17 May 2007, Jared Rhine wrote:

> I sent this email a couple days ago:
>
> http://lists.osafoundation.org/pipermail/chandler-dev/2007-May/008233.html
>
> but multiple people told me they didn't get a copy.  So a quick resend.  The 
> body:
>
> -------- Original Message --------
> Subject: 	[commits] (vajda) [14318] - fixed bug in trying to duplicate 
> a
> closed cursor
>
> - added CompactTask, a durable task compacting the repository every 7 days
>
> -----
>
> Am I reading this right, that every 7 days all Chandler users will have
> to confirm a dialog (or reject and get that dialog the next day)?

Yes, this is a 'courtesy'. The alternative is have chandler block the UI once 
a week for doing a compact for a few minutes to a bit more (on Esther's 
repository of 6500 versions, it ran in 3.5 hours).

In other words, if your repository got so big as to cause a lot of disk access 
when iterated to be compacted, your CPU usage goes down to 10% (or less) and 
your HDD usage goes to 100%. On a laptop, this can be v e r y  s l o w.

> I certainly understand how the functionality of compaction will be a
> benefit to end-users.  Just not too psyched at the UI aspects.  Has all
> the charm of a recurring Windows systray security popup.

:)

Andi..