• 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: GCD killed my performance
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: GCD killed my performance


  • Subject: Re: GCD killed my performance
  • From: Dave Fernandes <email@hidden>
  • Date: Fri, 25 Apr 2014 01:26:56 -0400

Is there any way to batch up more work to do in each block? Then your ratio of real work to overhead would go up.

On Apr 25, 2014, at 12:35 AM, Jens Alfke <email@hidden> wrote:

>
> On Apr 24, 2014, at 9:04 PM, Dave Fernandes <email@hidden> wrote:
>
>> What’s the CPU utilization? Are you actually getting full use of them, or are your threads blocked waiting for something?
>
> Fairly high — I think 175% or so (out of 200% possible). The problem is that a large fraction of that is taken up with busywork. In the CPU profile list from Instruments, the top 25 or so stack frames are all system infrastructure; you have to read down quite a ways to find any application code at all.
>
> —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


References: 
 >GCD killed my performance (From: Jens Alfke <email@hidden>)
 >Re: GCD killed my performance (From: Dave Fernandes <email@hidden>)
 >Re: GCD killed my performance (From: Jens Alfke <email@hidden>)

  • Prev by Date: Re: NSToolbarItem Action Not Passed to NSButton...
  • Next by Date: Re: GCD killed my performance
  • Previous by thread: Re: GCD killed my performance
  • Next by thread: Re: GCD killed my performance
  • Index(es):
    • Date
    • Thread