> On 1 May 2015, at 3:02 pm, Steve Mills <sjmi...@mac.com> wrote: > > I’ve run into this too, where letting the OS figure out how many operations > to queue at once doesn’t always work like a human wants it to work. I ended > up doing what you did - leave one for the main thread. > NSOperationQueueDefaultMaxConcurrentOperationCount really isn’t smart enough, > or they need to add another constant > NSOperationQueueDefaultMaxConcurrentButDontBeAJerkOperationCount. >
Well, it’s always gratifying to find I’m not alone ;) How did you figure out a value that leaves one for the main thread? The actual value returned is -1 for NSOperationQueueDefaultMaxConcurrentOperationCount, not the actual number it calculated. I guess there’s a way to get the number of cores, but that isn’t necessarily the whole story…? —Graham _______________________________________________ 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
