XCode: CPU heavy or disk heavy?


Recommended Posts

I'm debating a 13in Pro or 13in Air. I like both, prefer the resolution of the Air, but the ports/optical of the Pro. Neither are a make/break though.

Really what it comes down to is that I use XCode as one of my main apps. When compiling is it more CPU intensive or disk? And if i was to get an Air would I really notice the difference vs the CUP in the 13in?

As a side note I am looking at the i7 in both models.

Link to comment
https://www.neowin.net/forum/topic/1036447-xcode-cpu-heavy-or-disk-heavy/
Share on other sites

I would think compiling is more CPU-intensive because each time you compile, it has to convert your code to something else understood by Mac OS X.

I don?t think the hard drive would really make a difference because many files in an application are very small, and OSes are all bad when it comes to managing small files.

I am not an expert though?

It depends on the nature of projects you build and how you build them. Start with a Linux source tree and compile: you've got 45 minutes of disk thrashing ahead of you. You notice a cery large difference doung a build with an SSD drive instead of a 5400 rpm laptop drive. For the test - change - compile loop of development you typically only touch a small part of the source tree. While that reduces the gains of fast drives it also reduces the gains of many cored processors.

For my money, as a typical desktop app developer (more like iTunes, less like Photoshop) I'd want a few very fast cores (instead of many slower ones), as much ram as possible, and the fastest hard drive I can find. By far the slowest part of compiling is when you have to hit the disk : reducing that makes the whole process more responsive. Go build "hello world" and compare the amount of time the system spends waiting on disk access vs the time spent compiling or linking in gcc/Icc/etc. the choice is obvious in my opinion.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Latest leak spills potential details about the upcoming Google Pixel Watch 4 by Sagar Naresh Bhavsar Google is set to officially unveil the Pixel 10 series and the Pixel Watch 4 on August 20. The company shared a teaser video on YouTube, confirming the date and the devices. While details about the Pixel 10 have been emerging frequently, a new leak provides information about the upcoming Google smartwatch. Reliable leaker Evan Blass has shared multiple images, appearing to be promotional materials, on the social media platform X. The images allegedly hint at what the upcoming Google Pixel Watch 4, the latest Wear OS smartwatch from the company, could have in store. First up, Google Pixel Watch 4 will come with Gemini integration, which means it will be the default assistant going forward. As per the leak, the smartwatch will come in two sizes: 45mm and 41mm, similar to its predecessor. Both variants are purported to feature Google's Actua 360 display that can hit a peak brightness of 3,000 nits, allowing for better outdoor visibility, even in extreme sunlight. While the actual battery capacity isn't revealed, the 41mm Pixel Watch 4 is tipped to offer up to 30 hours of battery life, whereas the 45mm watch will offer up to 40 hours of juice. This includes the AOD (Always On Display) enabled. Charging is also getting a boost by 25% with the Quick Charge Dock. The Google Pixel Watch 4 will come with 40+ exercise modes, ECG, SpO2, breathing rate, heart rate variability, dual-frequency GPS, and loss of pulse detection. Google will also be offering two years of LTE data for free via Google Fi Wireless service on the purchase of the LTE model. The 45mm variant of the Pixel Watch 4 is rumored to be launched in three colors, while the 41mm is shown to have an extra color. Images via Evan Blass on X
    • Here ya go : https://shop.royalmail.com/special-stamp-issues/monty-python 
    • What is happening in the WNBA!    
  • Recent Achievements

    • Week One Done
      harveycoleman123 earned a badge
      Week One Done
    • First Post
      EzraNougat earned a badge
      First Post
    • One Month Later
      westDvina earned a badge
      One Month Later
    • Community Regular
      Bern@rd went up a rank
      Community Regular
    • Week One Done
      Joey Solo earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      664
    2. 2
      +FloatingFatMan
      196
    3. 3
      ATLien_0
      154
    4. 4
      Xenon
      132
    5. 5
      wakjak
      101
  • Tell a friend

    Love Neowin? Tell a friend!