Re: Archiving and strip. Why "Setting Mode" sucks.
Re: Archiving and strip. Why "Setting Mode" sucks.
- Subject: Re: Archiving and strip. Why "Setting Mode" sucks.
- From: Jens Alfke <email@hidden>
- Date: Wed, 15 Feb 2017 09:45:28 -0800
On Feb 14, 2017, at 6: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.
If it’s not CPU-bound, and not I/O-bound, then what is it doing? Calling sleep()? Try using `sample` on it to see what it’s spending time in. Only thing I can imagine is that it uses a ton of memory and your OS is swapping.
—Jens |
_______________________________________________
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