[Chandler-dev] Re: [Proposal] 3 Possible Hacks to Improve Performance

Mimi Yin wrote:
> I know it's the 11th hour to bring up this kind of thing, but Keith's 
> suggestion reminded of a different "performance-improvement" hack we 
> discussed pre-Preview: to limit the amount of "legacy" calendar data 
> we import and get rid of anything "older than a year".
>
> So there are 3 things we might be able to do to alleviate performance 
> pain:
>
> 1. Replace weekly auto-purge with auto-export/reload. (Would this 
> actually help?)
>
> 2. Auto-archive anything that was triaged to DONE more than 1 year?? ago
> - The simplest way to do this might be to take a snapshot of your 
> data, export it to an Archive.chex file that is timestamped so that if 
> you ever need it, you can always reload it into Chandler to take a 
> look at it.
> - We could eventually add a File menu item that allowed you to switch 
> easily between archived data sets and your current data set. (Sort of 
> like the way Andi's repo-switch feature worked.)
>
> 3. Discard anything older than 1 year
>
> Mimi
2) would definitely get my vote - presumably, repeating events would not
get swept up even though they may have originally been created more than
a year ago? I'm not sure it even needs to be auto: maybe as part of the
weekly purge, a message saying "You can prevent Chandler slowing down by
periodically archiving your completed items. Go to File > Archive" or
something along those lines.

Keith

Keith

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev