Re: NSOperation Efficiency
Re: NSOperation Efficiency
- Subject: Re: NSOperation Efficiency
- From: Kyle Sluder <email@hidden>
- Date: Tue, 04 Dec 2012 11:58:08 -0800
On Tue, Dec 4, 2012, at 10:15 AM, Gerriet M. Denkmann wrote:
> I have an app which uses NSOperations inside an NSOperationQueue. These
> operations do not do any I/O - just Cpu. No swapping is taking place.
>
> When I set [ self.operationQueue setMaxConcurrentOperationCount: 1 ] each
> operation takes on average 200 msec., measured by NSDate.
>
> With 2 concurrent operations, it takes not 100 msec but 110 - an extra
> 10%. Ok - some overhead is to be expected.
>
> With 4 ops it takes 70 instead of 50 - overhead 40% - rather a lot.
> With 8 ops it takes 60 instead of 25 - overhead 140%. or: 40% of the cpu
> is used by my operations, 60% is used by whom? And for what?
>
> Is this to be expected? Or does my app has some hidden flaws? If so,
> where should I start looking?
How many operations are you creating? We've found that with more than a
few hundred operations, NSOperationQueue is unusable.
--Kyle Sluder
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden