-
Notifications
You must be signed in to change notification settings - Fork 115
Build time or run time? #96
Comments
Hey, that's a good point about the simulator. The readme here should specify which to use. I when with ⌘-R because it represents real-world use cases, and I went with a stopwatch because I don't want this repo to have (or appear to have) scientific accuracy. This is all supposed to be relative measurements. I'll amend the readme with new instructions, do you want to submit the build time using an iPad Air 2, iOS 12? |
After using your parameter I got 27 seconds fresh build and 7 seconds incremental. |
I am thinking, if including simulator launch time is worth including? Updated my stats to include simulator restart and I see it takes about 30% of the measured time: So it looks like total time consists of
Most of the time I am noticing me waiting is for:
Usually, I already have the simulator app and simulator device running on the machine. |
Definitely. That's why the readme instructions say the incremental build should have the simulator already running:
This kind of gives a lower and upper bound for the machine. The longest you'd have to wait (for everything to happen) and the shortest you could expect to wait (a single change re-running in an active sim). |
First thank you for organizing this collective effort.
I want to ask that if we're using the build time with ⌘+B showed by Xcode by
sudo defaults write com.apple.dt.Xcode ShowBuildOperationDuration -bool YES
? I think this is a better bench compare to ⌘+R because people might be launching different simulators(for example I am running iPad pro 21.9 3rd Gen). I think different simulators might launch in different timeframe. Also the Xcode build time shows more accuracy, to the 3rd decimals , compare to a stopwatch. For example my build time is 16.641s, 17.478s in 2 tests, compare to when app shows in simulator which is around 27s with stopwatch.I will submit a pr with the correct number after your response.
The text was updated successfully, but these errors were encountered: