On 4 Dec 2012, at 19:01, "Gerriet M. Denkmann" <gerr...@mdenkmann.de> wrote:
> > On 5 Dec 2012, at 01:55, Mike Abdullah <cocoa...@mikeabdullah.net> wrote: > >> If your operations are purely CPU-bound, the whole point of GCD is to manage >> this for you. With the default number of concurrent operations, >> NSOperationQueue does exactly that. Have you tried with that setting? > > I have, and it makes my app unresponsive (i.e unusable) until all operations > have finished. > Triggered by making other app, active, then again my app. That suggests your operations aren't purely CPU-bound then. They're getting stuck waiting on something else. When that happens, GCD sees it as wasted CPU time so starts off the next bit of work anyway. _______________________________________________ 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
