Scenario request: Lots of workflows with lots of updates that have slow validators
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
Run <workflow-count> workflows that are sent<update-count>updates. Updates should have validators that reject a '' number of updates. The validation step should incorporate some non trivial amount of delay to emulate a real validator. These updates should do some minor work like an activity.
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 or tests. Start by reading the repository's existing load-generator scenarios and running the current generator; done means it can configure workflow and update counts, rejection percentage, validator delay, and minor activity work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- performance, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100