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, and the first try with the RAM disk took 19.  After that
it recorded some lower times, but essentially a minor improvement, if at
all.

A little surprising.

Anyway, determined to stick with the 2013 machine for a while longer, it's
still "good enough."



On Fri, Jun 28, 2019 at 4:58 PM Jeff Szuhay <j...@szuhay.org> wrote:

> 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 partition in
> memory. Then make that
> partition the “Derived Data” location.
>
> You can see how here: [
> http://www.blinddogsoftware.com/goodies/#CacheInYourPocket]
>
> If you notice an improvement in stability and decreased build time, great.
> If not, just keep
> on building great apps.
>
>
> On Jun 28, 2019, at 11:02 AM, Steve Mykytyn via Cocoa-dev <
> cocoa-dev@lists.apple.com> 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 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 commentary
> based on personal, direct experience.
>
>
>
_______________________________________________

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Reply via email to