yonaskolb / yonaskolb/XcodeGen
Performance regression since 2.2.0
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 8.8k
- Forks
- 908
- Avg merge
- 17d 14h
- Merged PRs (30d)
- 2
Description
We're a bit behind on updating XcodeGen, and when I went to test it today I found there to be a very large performance difference:
2.2.0:
Time (mean ± σ): 49.707 s ± 3.510 s [User: 46.404 s, System: 2.019 s]
Range (min … max): 45.022 s … 55.334 s 10 runs
2.6.0:
Time (mean ± σ): 94.183 s ± 8.082 s [User: 112.077 s, System: 3.114 s]
Range (min … max): 85.797 s … 112.238 s 10 runs
The tl;dr here is that the newest version is ~2x slower than the older one. I assume this might have something to do with underlying xcodeproj changes, but haven't dug in yet. I will try to spend some more time profiling this soon.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the reported benchmark with XcodeGen 2.2.0 and 2.6.0, then profile the generation command to locate the regression. Investigate the suspected underlying xcodeproj changes; done means identifying and addressing the cause so the newer version no longer shows the reported roughly 2x slowdown.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- cli, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100