Skip to content

MacBook Pro 16 (2019) - i9 2.3 GHz- 32 GB - Xcode 13.3#323

Open
ghost wants to merge 379 commits intoswift-build-systemfrom
master
Open

MacBook Pro 16 (2019) - i9 2.3 GHz- 32 GB - Xcode 13.3#323
ghost wants to merge 379 commits intoswift-build-systemfrom
master

Conversation

@ghost
Copy link

@ghost ghost commented Apr 4, 2022

Checklist

If you have any non-Apple hardware components - submit your results to the Custom Hardware table.

  • I performed all steps to correctly run XcodeBenchmark.
  • I used Xcode 12.5 or above.
  • I attached a screenshot with a compilation time and other fields, example.
  • I confirm that Time column is still sorted.
  • The content in cells is centered.

Screenshot 2022-04-04 at 20 27 31

devMEremenko and others added 30 commits July 26, 2023 00:23
Macbook Pro 16" 2021 (macOS Ventura), 87 sec
no optimizations done to the system, fresh out of the box
…_71_sec

[Xcode 15] M3 Max 16-core 64GB RAM | 71.5 sec
Mac Studio Mac14,14 M2 Ultra 24-core 192 RAM, 2TB SSD with XCode 15
2018 MacBook Pro 15" - 348 secs
devMEremenko and others added 30 commits May 9, 2025 21:50
Added result for iMac19,2 21.5" 2019
added chart for Xcode 26; test conducted on m4 air running tahoe
Mac Studio 2023 M2 Ultra 24 Cores 128GB 2TB | 65s
Macbook Pro M3 Max 14-inch result
Macbook Pro 13" 2021 M1 Pro 8 Cores 32GB 512GB | 175s
Removed previous Xcode 16 results section and updated device listing.
Xcode 26.1 - Mac Mini M2 Pro 16GB / 512GB
Incorrect CPU description. Should be M4 instead of M2.
Add Mac Studio 2023 with M2 Ultra specifications to ReadMe.md
Xcode 26.1 - MacBook Air (2020) - M1 - 8GB / 256GB
Add MacBook Pro 14" 2023 M2 16GB and MacBook Pro 14" 2024 M4 24GB
Removed the Mac mini 2023 entry from the specifications table because it most likely contains stale results (due to the recent XcodeBenchmark update). Waiting for new submissions.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.