Scenario request: Lots of namespaces with varying amounts of traffic
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 102
- Forks
- 29
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 22
Description
Describe the scenario you'd like
Create <namespace-count> namespaces, then run <workflow-count> workflows across them with <frequency> frequency on each <configurable-percent> percent. Basically need to have some amount of namespaces busy, some less busy, some mostly idle, etc.
The variables can be set based on good numbers that stress the environment.
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, so begin by locating the existing scenario and load-generation configuration in the repository. The work is done when namespace count, workflow count, frequency, and the percentage of namespaces receiving each traffic level can be configured to produce busy, lightly used, and mostly idle namespaces.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- performance, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100