• 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: Archiving and strip. Why "Setting Mode" sucks.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Archiving and strip. Why "Setting Mode" sucks.

  • Subject: Re: Archiving and strip. Why "Setting Mode" sucks.
  • From: Alex Zavatone <email@hidden>
  • Date: Fri, 17 Feb 2017 01:49:52 -0600

On Feb 15, 2017, at 9:27 AM, Chris Cleeland wrote:

Source to strip is here:

https://opensource.apple.com/source/cctools/cctools-895/misc/strip.c.auto.html

Doesn't use multiple threads, which probably makes sense from a simplicity perspective.  If you have multiple cores, is there anything akin to the "-j" option for GNU Make that will fire off multiple jobs simultaneously?  At that point it becomes an issue of whether the dependencies are set up to permit concurrent strip of object files.

That would be awesome, or at least a scheduler instead of only using 1 process on 1 core.  

I hope to find out what's limiting it, because it doesn't appear to be drive throughput bound and with 40 GB of RAM, it's not memory bound.


On Tue, Feb 14, 2017 at 8:26 PM, Alex Zavatone <email@hidden> wrote:
I just found out that archiving and when "Setting Mode",  strip is only using 5% of 1 core no matter how many are free cores there are on the current Mac.  Strip is also not disk bound.

Just tried this across 3 Macs while archiving.  Apparently, strip is single threaded and takes tens of seconds stripping symbols from intermediate files while never going over 5% CPU utilization on one core.

One question.  Why?

One more question.   Is it possible to renice strip so it is not so terribly slow?

I have Mac Pros that take LONGER than MacBooks to create an iOS archive in Xcode 8 because of this.

The Mac Pros a 6 core Cylinder and 12 core Tower with PCI SSD and > 40 GB of RAM while the MBPs are 2012 and 2014 4 core i7s with 16 GB of RAM, running off of SSDs.

Any clue why this is so slow?

Thanks,
Alex Zavatone
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden


 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden
  • Follow-Ups:
    • Re: Archiving and strip. Why "Setting Mode" sucks.
      • From: Chris Cleeland <email@hidden>
References: 
 >Archiving and strip. Why "Setting Mode" sucks. (From: Alex Zavatone <email@hidden>)
 >Re: Archiving and strip. Why "Setting Mode" sucks. (From: Chris Cleeland <email@hidden>)

  • Prev by Date: Re: Archiving and strip. Why "Setting Mode" sucks.
  • Next by Date: Re: Archiving and strip. Why "Setting Mode" sucks.
  • Previous by thread: Re: Archiving and strip. Why "Setting Mode" sucks.
  • Next by thread: Re: Archiving and strip. Why "Setting Mode" sucks.
  • Index(es):
    • Date
    • Thread