• 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: Spinning the busy indicator
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Spinning the busy indicator


  • Subject: Re: Spinning the busy indicator
  • From: Uli Kusterer <email@hidden>
  • Date: Fri, 01 May 2015 13:18:32 +0200

On 01 May 2015, at 06:46, Graham Cox <email@hidden> wrote:
> I use NSOperationQueue with the default -maxConcurrentOperationCount which is NSOperationQueueDefaultMaxConcurrentOperationCount, i.e. let the system figure it out. That appears to create 4 threads for my particular machine, which has a Core i3 (2 cores) CPU. My peak CPU usage is reported as 418%. I’m not sure how it achieves that from a dual core CPU, but one would assume that Apple know what they’re doing [/irony].

Does your Core i3 do HyperThreading? In that case, there are a second set of virtual CPUs, so that when one blocks, a second thread can get swapped in *at the hardware level* and get cycles.

Cheers,
-- Uli Kusterer
“The Witnesses of TeachText are everywhere...”
http://zathras.de


_______________________________________________

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


  • Prev by Date: Re: Spinning the busy indicator
  • Next by Date: Re: Spinning the busy indicator
  • Previous by thread: Re: Spinning the busy indicator
  • Next by thread: Re: Spinning the busy indicator
  • Index(es):
    • Date
    • Thread