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: Alex Zavatone <email@hidden>
- Date: Fri, 17 Feb 2017 01:51:56 -0600
On Feb 15, 2017, at 12:23 PM, Anders Montonen wrote: On 15 Feb 2017, at 19:45, Jens Alfke < email@hidden> wrote: 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. I bet it’s a measuring artifact. Each invocation of strip will take far less time than the sampling interval, and will show as taking a tiny portion of CPU time, even though it might have consumed a full core while running. You see the same effect in Activity Monitor, top and Process Explorer (on Windows). Increasing the sampling rate, or monitoring created and destroyed processes will usually give a better idea of what’s really going on.
I've got the sampling rate maxed and I'm watching the output of what's being processed in Xcode and in the Activity Monitor, I'm filtering on strip. I'll try top next.
|
_______________________________________________
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