On Dec 4, 2012, at 7:33 PM, Kyle Sluder <k...@ksluder.com> wrote: > Yeah, it sounds like you're saturating the thread pool due to > non-CPU-bound operations. NSOpQ is going to spend its entire time > spawning and switching to threads while you append more and more > operations to the queue.
Apologies, but I have trouble believing that. Isn’t NSOperationQueue just a thin veneer around GCD? A few thousand tasks shouldn’t cause a performance problem. What’s your evidence that it does? —Jens _______________________________________________ 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
