There used to be a control panel for this but Instruments lets you disable
hyper threading and cores that is a systemwide setting.
The guys over at PSODFKit got distcc working with ccache for “stupid fast
builds” in Objective-C.
https://pspdfkit.com/blog/2017/crazy-fast-builds-using-distcc/
> On Jun 28, 2019, at 9:39 PM, Dave Fernandes via Cocoa-dev
> wrote:
>
> Not a comprehensive list, but a start...
> https://github.com/ashfurrow/xcode-hardware-performance
Very interesting. Thanks for sharing.
I was surprised to see Custom Hackintosh machines contributing to the Xcode
build
The framework I'm building is written in Objective-C. I'm waiting for
Swift to stabilize...
Looking at Activity Monitor during the build, all four CPU cores are
utilized symmetrically, the four hyper-threads somewhat less. The disk IO
doesn't look like it's a bottleneck either. It does seem
Thanks for all the advice. I set up the 4GB RAM disk, verified it was
putting Derived Data there, and tested against a dynamic framework I build
often. I even rebooted to have a clean starting point.
The results were not great. The framework normally takes between 13 and 17
seconds to build,
Not a comprehensive list, but a start...
https://github.com/ashfurrow/xcode-hardware-performance
> On Jun 28, 2019, at 2:02 PM, Steve Mykytyn via Cocoa-dev
> wrote:
>
> My main Xcode machine is a late 2013 27-inch iMac, 24GB RAM, 3.5 GHz Core
> i7 with 500GB SSD.
>
> It works fine, but I'm
Compilation is largely an i/o-bound problem. Unless the projects you work on
are hideously
large and would benefit from parallel processing (splitting the i/o among
several processors),
your current machine is quite satisfactory.
Try this: using your current system, create a 4GB disk
My main Xcode machine is a late 2013 27-inch iMac, 24GB RAM, 3.5 GHz Core
i7 with 500GB SSD.
It works fine, but I'm wondering if an iMac Pro or a top-of-the-line 2019
iMac would be a life-changing experience. Or just, "that's nice."
The Geekbench numbers are somewhat informative, but hoping for
