Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. We have updated the language to the Editor Terms based on feedback from our employees and community. Learn more.
    Dismiss Notice
  3. Join us on November 16th, 2023, between 1 pm and 9 pm CET for Ask the Experts Online on Discord and on Unity Discussions.
    Dismiss Notice

Is it normal that my builds can take up to 2 hours?

Discussion in 'iOS and tvOS' started by GeorgeCH, Dec 14, 2017.

  1. GeorgeCH

    GeorgeCH

    Joined:
    Oct 5, 2016
    Posts:
    222
    EDIT: Sorry, can a mod please move this to he iOS forum? I stupidly posted in the wrong one - I guess that’s what 2.5h build of your first-ever App Store submission can do to one’s sanity!

    Hi all -

    I develop on PC, then export an iOS build which I then compile in Xcode, archive, and finally upload. I do not use Cloud Build.

    My usual build times are as follows:
    • Preparing the iOS build on PC: 1 min
    • Archiving: 20 - 25 min
    • 1st half of compilation (until it gets the option screen where you select whether to include BitCode): 40 - 6 min
    • 2nd half of compilation (which ends with exporting the IPA file): 20 - 25 min
    • Total build time: 80 - 110 minutes
    I use a Mac Mini, and my project isn't exactly complex - it's a fairly simple incremental clicker game, clocking in at about 70mb of assets, no 2D or physics. Most of my time is spent looking at the "Fetching App Store Configuration" screen in Xcode.

    Are these build normal on Mac for a project of this scope? I'm wondering whether this is a hardware issue (after all, a Mac Mini is a potato, and I think mine is even running 4GB RAM!) and whether getting a high-end MBP would significantly improve the issue.
     
    Last edited: Dec 14, 2017
  2. BrianND

    BrianND

    Joined:
    May 14, 2015
    Posts:
    79
  3. andymads

    andymads

    Joined:
    Jun 16, 2011
    Posts:
    1,614
    As I was just about to do a build when I read this I thought I'd time the various parts.

    I'm using a 2011 iMac. 48.5Mb assets. IL2CPP Universal / Release / Non-development build.

    Build in Unity: 4m
    Build for running in Xcode: 4m
    Archive in Xcode: 9m
    Export Ad-Hoc IPA: 1m
    Export App Store IPA: 1.5m
     
  4. GeorgeCH

    GeorgeCH

    Joined:
    Oct 5, 2016
    Posts:
    222
    Interesting!

    I bought my Mac Mini this year, but seeing as it hasn't been refreshed since 2014, the model is quite old. I also opted for the cheapest model (1.4Ghz CPU, 4GB RAM, and an HDD drive). In general, this consistently leads to even regular, non-Xcode applications running extremely sluggishly (Chrone can take 10-15s seconds to open from start-up, Xcode's open time approaches 60 seconds, and almost every mouse click result in that multi-colored spinning circle appearing for 3-4 seconds).

    Compared to the 2011 iMac, RAM is the same (unless you configured it for more) but the iMac's CPU is 2.5-2.7. I'm starting to wonder whether the build speeds I'm seeing are down to my hardware.
     
  5. andymads

    andymads

    Joined:
    Jun 16, 2011
    Posts:
    1,614
    Yeah, I did. I have 12Gb.