[Chandler-dev] Pre-loading items as a performance optimization
Morgen Sagen
morgen at osafoundation.org
Wed Oct 4 12:45:13 PDT 2006
On Oct 4, 2006, at 11:47 AM, Jeffrey Harris wrote:
> Hi Morgen,
>
>> Come to think of it, you would think the minical would trigger the
>> loading of a couple months worth of events anyway. Does the minical
>> manage to *not* load events in its range? Ah, but the minical only
>> displays events that are in "Mine" collections, and this
>> particular test
>> collection is probably not designated as Mine. So as currently
>> implemented, my guess is that all Dashboard items occurring in the
>> current and following month are loaded anyway.
>
> The minical does avoid generating occurrences, it needs to
> determine how
> big to make busy bars, but it doesn't need occurrences to do that, it
> looks at the recurrence rule on the master (and any modifications) to
> calculate them for recurring events.
>
> Sincerely,
> Jeffrey
So ironically, if the minical went ahead and generated occurrences
and loaded all events in its range, week-jumping would be faster. :-)
More information about the chandler-dev
mailing list