Skip to content
This repository has been archived by the owner on Jun 19, 2022. It is now read-only.

Document broker stress testing scenarios #1500

Closed
grantr opened this issue Jul 22, 2020 · 3 comments
Closed

Document broker stress testing scenarios #1500

grantr opened this issue Jul 22, 2020 · 3 comments
Labels
area/broker kind/doc kind/feature-request New feature or request priority/1 Blocks current release defined by release/* label or blocks current milestone release/2
Milestone

Comments

@grantr
Copy link
Contributor

grantr commented Jul 22, 2020

Problem
We need a list of standard test scenarios to use when probing the broker's performance characteristics. Related to #1489, #1490, and #1491.

The test scenarios should be designed to push the broker to its limits and beyond, but based on realistic customer use cases and performance targets.

Persona:
Contributor

Exit Criteria
A document listing test scenarios

Additional context (optional)
Some useful scenarios have been documented at #876, #1254, and #1265.

@grantr grantr added kind/feature-request New feature or request area/broker priority/1 Blocks current release defined by release/* label or blocks current milestone release/2 labels Jul 22, 2020
@grantr grantr added this to the Backlog milestone Jul 22, 2020
@grantr grantr modified the milestones: Backlog, v0.17.0-M2 Jul 22, 2020
@liu-cong liu-cong removed their assignment Jul 29, 2020
@liu-cong
Copy link
Contributor

I unassigned myself for now as I don't think I will get to it this week.

@yolocs
Copy link
Member

yolocs commented Aug 4, 2020

@grantr @grac3gao Do you think the scenarios here https://github.com/yolocs/ce-test-actor/tree/master/scenarios are good enough to close this issue? For all the problems we have detected, it doesn't seem we went beyond these scenarios (some parameters might be different from the generated yamls).

@grantr
Copy link
Contributor Author

grantr commented Aug 5, 2020

I think those scenarios are a good start, but to close this issue they need to be documented in this repo (ideally with a link to the scenario directory in the ce-test-actor repo).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area/broker kind/doc kind/feature-request New feature or request priority/1 Blocks current release defined by release/* label or blocks current milestone release/2
Projects
None yet
Development

No branches or pull requests

3 participants