Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Run internal 'realistic' tests on Broker Scaling #15517

Closed
Tracked by #13642
ghost opened this issue Dec 7, 2023 · 0 comments · Fixed by camunda/zeebe-chaos#471
Closed
Tracked by #13642

Run internal 'realistic' tests on Broker Scaling #15517

ghost opened this issue Dec 7, 2023 · 0 comments · Fixed by camunda/zeebe-chaos#471
Assignees
Labels
area/performance Marks an issue as performance related area/test Marks an issue as improving or extending the test coverage of the project

Comments

@ghost
Copy link

ghost commented Dec 7, 2023

Run a few internal tests on Broker Scaling in a 'realistic' setting, i.e., mimicking the production setups that customers might have (in terms of workload, cluster setup, etc.)

Show metrics/graphs (throughput, latency, etc.) as as result of the tests.

@ghost ghost assigned lenaschoenburg Dec 7, 2023
@ghost ghost changed the title Run internal tests on Broker Scaling Run internal 'realistic' tests on Broker Scaling Dec 7, 2023
@lenaschoenburg lenaschoenburg added area/performance Marks an issue as performance related area/test Marks an issue as improving or extending the test coverage of the project labels Dec 7, 2023
lenaschoenburg added a commit to camunda/zeebe-chaos that referenced this issue Dec 22, 2023
This combines three experiments @deepthidevaki and I did today, all
relating to dynamic scaling and performance.

Closes #456
Closes #457
Closes camunda/camunda#15517
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/performance Marks an issue as performance related area/test Marks an issue as improving or extending the test coverage of the project
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant