• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: NSOperation Efficiency
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NSOperation Efficiency


  • Subject: Re: NSOperation Efficiency
  • From: Jens Alfke <email@hidden>
  • Date: Tue, 04 Dec 2012 20:00:59 -0800

On Dec 4, 2012, at 7:33 PM, Kyle Sluder <email@hidden> 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 (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


  • Follow-Ups:
    • Re: NSOperation Efficiency
      • From: Kyle Sluder <email@hidden>
    • Re: NSOperation Efficiency
      • From: Kyle Sluder <email@hidden>
References: 
 >NSOperation Efficiency (From: "Gerriet M. Denkmann" <email@hidden>)
 >Re: NSOperation Efficiency (From: Kyle Sluder <email@hidden>)
 >Re: NSOperation Efficiency (From: "Gerriet M. Denkmann" <email@hidden>)
 >Re: NSOperation Efficiency (From: Kyle Sluder <email@hidden>)

  • Prev by Date: Re: NSOperation Efficiency
  • Next by Date: Re: NSOperation Efficiency
  • Previous by thread: Re: NSOperation Efficiency
  • Next by thread: Re: NSOperation Efficiency
  • Index(es):
    • Date
    • Thread