Capgen performance when using many suites
Open
Nobody has claimed this yet.
capgen
capgen-unification
enhancement
- Dominant language
- Python
- Stars
- 25
- Forks
- 67
- Avg merge
- 3d 8h
- Merged PRs (30d)
- 2
Description
Description
When comparing to to Prebuild (~12s), Capgen (~230s) takes ~20x longer when building all of the suites for the CCPP SCM.
I added timers to the main capgen routine:
Related to (optional)
Needed for Prebuild to Capgen transition.
Contributor guide
No contributing guide indexed for this repository
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
Start with the main Capgen routine and the CCPP SCM suite list linked in scm/src/suite_info.py. Reproduce the timing comparison while building all suites, then use the reported timers to identify where Capgen spends its time. Done means addressing the bottleneck and verifying the all-suites runtime with the same comparison.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- performance, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100