RFE: Output report of the slowest operation after a build
- Dominant language
- Python
- Stars
- 140
- Forks
- 45
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 6
Description
[See original issue on GitLab](https://gitlab.com/BuildStream/buildstream/-/issues/887)
In GitLab by [[Gitlab user @jjardon]](https://gitlab.com/jjardon) on Jan 30, 2019, 13:29
## Background
When you are building a big project, It would be nice to have a report of the slowest operations so can focus in the ones that takes more time
Bonus points if you can configure some of the output:
- Number of operation
- Count build task/ download task/ or both
## Acceptance Criteria
- BuildStream outputs the 20 slowest operations
Contributor guide
Research direction
Start by locating the build completion output or reporting entry point in BuildStream; the issue does not name a file or test. Implement reporting of the 20 slowest operations, then verify that a build displays those operations and their durations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system, performance
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100