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

Hi Mimi,

> 1. Replace weekly auto-purge with auto-export/reload. (Would this 
> actually help?)

I think this would work.  Making it work smoothly and in a 
fault-tolerant way would take some thought, though.  Does it run at 
shut-down?  Start-up?

> 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.)

I don't really see this working very well with sharing and recurrence, 
and I think it would take a lot of work to get it right.

> 3. Discard anything older than 1 year
> 
> Of course, all of these things would be optional (except for maybe #1) 
> accompanied by an explanation that if you feel like Chandler is getting 
> sluggish, you should do them.

This terrifies me.  I can't quite say why, I guess there's no reason 
users shouldn't be allowed to do this, but opportunities to shoot 
yourself in the foot seem plentiful with a path like this.

Sincerely,
Jeffrey
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

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