[Chandler-dev] Performance of first time view switch
vs subsequent switching
D John Anderson
john at osafoundation.org
Tue Feb 13 17:03:11 PST 2007
On Feb 13, 2007, at 12:14 PM, Heikki Toivonen wrote:
> D John Anderson wrote:
>> Actually it's a little more complicated than this.
>> There are 3 situations:
>> 1) we need to copy a new tree of blocks and need to attach new
>> 2) we can reuse a cached copy but need to attach new contents
>> 3) we can reuse a copy and don't need to attach new contents
> Does that also cover the case where we have everything loaded into
> memory vs. things coming from disk? I.e. cases where you have had
> Chandler running for a while and have switched already between
> collections, and the case where you shut that Chandler instance and
> restart it with the same repository?
No, that's a separate dimension
> It is starting to look like we can't reasonably measure all cases.
> So do
> we continue the status quo or measure something else? And if something
> else, what is that?
I think we should start with a simple that measures the most
important case first then add extra tests for the other cases in
order of importance to the user.
So for starters I'd create a test that measures time switching
between two views, dashboard and calendar with different contents
after you've already visited the views once since launching Chandler.
> Heikki Toivonen
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> Open Source Applications Foundation "chandler-dev" mailing list
More information about the chandler-dev