[Chandler-dev] What is next for Chandler desktop?

[D John Anderson]

I think we need to first do some detailed measurements to decide what  
our performance priorities should be.

I suggest this based on my experience working on search performance  
of a giant repository. My intuition about what was slowing things  
down wasn't very good. After a little poking around it looked like  
notifications relating to calendar events swamped out most of the  
other performance problems, but those notifications were only a  
problem some of the time -- other times performance seemed very  
reasonable.

John

On Sep 10, 2007, at 3:39 PM, Andi Vajda wrote:

>
> On Mon, 10 Sep 2007, Grant Baillie wrote:
>
>> Yes, that is a more reasonable number, (although you need to make  
>> sure that users can import large amounts of email in a "finite"  
>> length of time). I'm more concerned about Chandler's memory/disk/ 
>> CPU usage with, say, 75,000 total mail items in the repository (a  
>> number I took from my current mail client ... others may vary).
>
> Last time I tried to import 6000 mail messages, it took about 18  
> minutes on my mac. Not a speed demon but definitely bounded. Brian  
> added feedback about the import to the message window and the user  
> can see progress.
>
> Having 75,000 messages in the repository remains to be tested, indeed.
> Not all of them would be loaded into memory at the same time, I  
> presume...
>
> Andi..
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>
> Open Source Applications Foundation "chandler-dev" mailing list
> http://lists.osafoundation.org/mailman/listinfo/chandler-dev