Re: NSMetadataItem performance issues
Re: NSMetadataItem performance issues
- Subject: Re: NSMetadataItem performance issues
- From: Hamish Allan <email@hidden>
- Date: Thu, 4 Aug 2005 15:10:20 +0100
On 3 Aug 2005, at 17:55, Vince DeMarco wrote:
You get this quickly you need to do a bulk fetch using the Sortiing
attributes of MDQueryRef()
I think I must be missing something. If I set the sort descriptors of
an query, it still doesn't cause the attributes to be copied, right?
That's the whole point of having the sorting performed "server side",
isn't it -- so that the attributes *don't* have to be copied?
and the two calls.
MD_EXPORT CFIndex MDQueryGetIndexOfResult(MDQueryRef query, const
void *result) MD_AVAIL;
and
MD_EXPORT const void *MDQueryGetResultAtIndex(MDQueryRef query,
CFIndex idx) MD_AVAIL;
I also don't want either to get an index from a result, or to get a
result from an index. I just want to get a copy of certain attributes
from a result I already have a reference to, so that I can put them
in a table!
Its not a mutex issue, each call to MDItemCopyAttribute() involves
a mach_message to the server, a context switch and a mach_message
back to you to return the result.
But why does the same operation sometimes take 1ms and sometimes
1000ms? And why, specifically, do those times when it takes 1000ms
only ever occur when it's called from the table redrawing code,
rather than in one of the tens of thousands of times it's called from
my NSMetadataQueryGatheringProgressNotification handler?
Thanks,
Hamish
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden