slimtoolkit / slimtoolkit/slim
Ability to run http probes concurrently to decrease build time
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.4k
- Forks
- 841
- PR merge metrics
- No merged PRs in 30d
Description
The ability to run http probes concurrently (up to a defined number of requests) could greatly decrease the build time -- especially when probing IO bound features of an application in an image. It appears that only the http probe crawler feature has such a concurrency feature.
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
Start by locating the existing HTTP probe crawler concurrency implementation and comparing it with the other HTTP probe paths. Define how a configurable request limit should apply, then verify that concurrent probing reduces build time without changing probe results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- devops, networking, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100