MDmdswanson·Dec 30, 2023
Just to add: https://github.com/devMEremenko/XcodeBenchmark
In Tracking developer build times to decide if the M3 MacBook is worth upgradingdevMEremenko
XcodeBenchmark
Python2020–2026
devMEremenko / XcodeBenchmark
XcodeBenchmark
XcodeBenchmark measures the compilation time of a large codebase on iMac, MacBook, and Mac Pro
8Distinct people
8Mentions
0Explicit recommenders
3.7KGitHub stars
What to know before exploring
What it is
XcodeBenchmark measures the compilation time of a large codebase on iMac, MacBook, and Mac Pro
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 6:01:08 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year8 dated mentions
Observed mentions: 2020-12-03 22:56:59 UTC to 2026-03-04 03:18:12 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 3 | 0 | 3 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 2 | 1 | 1 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
3 sourcesMy personal research for iOS development, taking the cost into consideration, concluded:
- M2 Pro is nice, but the improvement over 10 core (8 perf cores) M1 Pro is not that large (136 vs 120 s in Xcode benchmark: https://github.com/devMEremenko/XcodeBenchmark)
- M3 Pro is nerfed (only 6 perf cores) to better distinguish and sell M3 Max, basically on par with M2 Pro
So, in the end, I got a slightly used 10 core M1 Pro and am very happy, having spent less than half of what the base M3 Pro would cost, and got 85% of its power (and also, considering that you generally need to have at least 33 to 50 % faster CPU to even notice the difference :)).
In Tracking developer build times to decide if the M3 MacBook is worth upgradingYes, they have the same cores but the memory bandwidth is double the speed: “M2 Pro’s memory maxes out at 32GB, but the M2 Max can handle as much as 96GB. And memory bandwidth on the M2 Max is double that on the M2 Pro”.
You can see here the M2 Pro got an 80 benchmark and the M2 Max, the line above the commit, got a 72 (arbitrary numbers, for sure, but a real difference!):
https://github.com/devMEremenko/XcodeBenchmark/pull/393/comm...
In Ask HN: Desktop vs. Laptop with ARM/Apple Silicon