devmeremenko/xcodebenchmark

XcodeBenchmark measures the compilation time of a large codebase on iMac, MacBook, and Mac Pro

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 56 minutes ago
Added to GitGenius on September 18th, 2026
Created on August 18th, 2020
Open Issues & Pull Requests: 345 (+0)
GitHub issues: Enabled
Number of forks: 413
Total Stargazers: 3,668 (+0)
Total Subscribers: 48 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 16.7 hours
Mean response time: 81.1 days
90th percentile: 62.3 days
Tracked items: 19

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 70
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 465 days
Stale 30+ days: 70
Stale 90+ days: 69

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

XcodeBenchmark is a benchmarking tool that measures Mac compilation performance by building a large Swift codebase in Xcode.

The tool addresses the practical problem of evaluating whether a Mac purchase or upgrade will meaningfully improve Xcode build times. It works by compiling a substantial codebase on target machines and recording the time required, providing real-world performance data across different Mac models, processor configurations, and Xcode versions. This approach yields concrete numbers that developers and companies can use when making hardware purchasing decisions.

Anyone considering adoption should use this tool if they are evaluating Mac hardware for Swift development work and want empirical data on compilation performance. It suits organizations making bulk hardware purchases or individuals deciding between Mac models at different price points. The tool is most valuable when the specific Mac configuration you are considering has already been benchmarked and published in the results table, allowing direct comparison. If your target device is not yet listed, the project maintains open issues and pull requests where community members can contribute new benchmark results.

The project maintains an active benchmark database with results across multiple Xcode versions and a wide range of Mac hardware configurations. Community contributions of new benchmark results are actively solicited and tracked through the issue and pull request system. The project has been updated to support current Xcode releases, with explicit notes about compatibility between different Xcode versions to prevent invalid comparisons across incompatible builds.