Trepan-Debuggers / Trepan-Debuggers/remake
Possible Enhacement Idea
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 850
- Forks
- 80
- PR merge metrics
- No merged PRs in 30d
Description
When I first look at a build to profile I normally find the box with the most cores on it and run /usr/bin/time -v make -j NumOfCPU
I then look at Percent of CPU this job got: in the output of time from the build command. If it is close to the number of cores I gave the make command then I know I can probably look into things like dist_cc or icecreamcc to get faster builds, but if I gave that thing 24 cores and it only got a 800% then things like dist_cc or icecreamcc aren't going to do any good because I couldn't even uses all the cores on my current box all the way.
It might be nice if remake could give us some data or stats on how busy the make job queue is during the build. Average Job Queue length, How much time it spent with a full job queue and maybe if it never hit the max number of jobs in the queue.
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
The issue names no files, tests, or entry points. First inspect remake's build execution and job-queue handling to determine where queue length and utilization could be measured; done would require an agreed design and validation for average queue length, time at capacity, and whether the queue reached its limit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- build-system, devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100