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

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.

****
I'm loathe to start up a conversation about more features at this point in the process, but given the feedback we've received on performance, does 1.0 need to demonstrate some concrete progress on performance since Preview? Would the above fixes help the people who are feeling performance pain today? Or are they not likely to improve the situation by very much?

Mimi


On Jul 7, 2008, at 4:15 PM, Keith Winsor wrote:

Mimi Yin wrote:
Would it make any sense to replace the weekly "Purge" with a weekly automatic "Export/Reload"?(Assuming that the primary purpose of Purge is to speed things up.)

Some users have reported that Reload seems to speed things up more than Purge.

Mimi
Mimi,

Are there any plans for what I would normally refer to as a purge facility: the ability to tell Chandler to delete all tasks/events/ notes (user-selectable) created/completed before a given date. My 18,000 item repository probably has the potential to start slowing things down a bit soon...

All the best,

Keith
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

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

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

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

Reply via email to