On Sep 9, 2008, at 9:36 PM, Seth Willits wrote:
Surely adding 330 items to an array shouldn't take a minute on any machine from this century. I think your code is doing something you're not realizing. You could: a) have a method that on each observation explicitly creates a bajillion objectsb) have a bajillion observers that each create a bunch of objectsc) have enough observers and have enough oddly placed observations and method calls that you literally end up calling the same methods over many many times because it recurses unintentionally, for each object added to the array.
It might very well be something I don't realize. Shark tells me that all the time is spent in AppKit and Foundation, not in my code. (I can email the Shark session if you're interested, its 3.8 MB).
At the center of the problem (judging from the shark call stack) is NSCollectionView which causes all those burned cycles. If that collection view is swapped out and replaced by NSOutlineView, the whole thing gets very snappy. Of course there's no custom NSView and registering observers going on then.
I have had a lot of speculation following here but there's no point for that. Fact is as soon as I add observers to the objects that are being represented by the collection view, things get excruciatingly slow.
Regards Markus -- __________________________________________ Markus Spoettl
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
