On 20 Jan 2008, at 7:33 PM, Adam R. Maxwell wrote: > > On Jan 20, 2008, at 10:21 AM, Christiaan Hofman wrote: > >> >> On 20 Jan 2008, at 7:08 PM, Adam R. Maxwell wrote: >> >>> >>> On Jan 20, 2008, at 9:52 AM, Christiaan Hofman wrote: >>> >>>> >>>> On 20 Jan 2008, at 5:56 PM, Adam R. Maxwell wrote: >>>> >>>>> >>>>> On Jan 20, 2008, at 8:35 AM, Christiaan Hofman wrote: >>>>> >>>>>> Would it be possible to initialize the SKIndexRef on the thread >>>>>> rather than in init? I find that initializing the cached index >>>>>> blocks >>>>>> the UI for a very noticeable time. I think the index can be >>>>>> accessed >>>>>> on the main thread only in the -index method and in - >>>>>> cancelForDocumentURL:. >>>>> >>>>> Can you check with Shark or Spin Control to see what's slow? >>>>> Initializing the index on the thread would require avoiding >>>>> NSFileManager, unless it's only the SKIndex creation that's slow. >>>>> >>>> >>>> It seems to spend a lot of time unarchiving (14.5% in Shark). About >>>> half comes from +indexCachePathForDocumentURL: and half from >>>> unarchiving the index we're actually using (I have 2 cached >>>> indexes, >>>> the one I use here is significantly larger than the other). >>> >>> That's what I was afraid of (unarchiving). How big is the actual >>> archive in MB? Mine at work has ~500 files indexed, and I didn't >>> see >>> any slowdown or beachball. >>> >> >> It's about 50 MB, indexing about 2/3 of about 1000 items. I did some >> dumb timing in the initializer, and getting the cache path and >> unarchiving step are indeed the slowest. SKIndexOpenWithMutableData >> was pretty fast. > > Wow! That explains it; my index was < 10 MB. > > Yet another thing we might try is archiving objects separately instead > of in an NSDictionary. Then we could use -[NSKeyedUnarchiver > initForReadingWithData:[NSData dataWithContentsOfMappedFile:]] to > unarchive only the document URL instead of the full root object > graph. That assumes NSKeyedUnarchiver doesn't need to read the entire > file into memory just to archive a single key, of course. > > -- > adam
It would still require a full unarchiving of the cached index we want. Christiaan ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Bibdesk-develop mailing list Bibdesk-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-develop
