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.

Sign up for GitHub

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

Jump to bottom

Hypothesis: Bigger state shouldn't make an impact on Throughput #64

Open
ChrisKujawa opened this issue Oct 27, 2021 · 2 comments
Open

Hypothesis: Bigger state shouldn't make an impact on Throughput #64

ChrisKujawa opened this issue Oct 27, 2021 · 2 comments
Labels
Contribution: Performability This issue will contribute to build up confidence in performability. Hypothesis A thing which worries us and is ready for exploration. Impact: High The issue has an high impact on the system. Likelihood: Medium The issue is not so likely.

Comments

@ChrisKujawa
Copy link
Member

Hypothesis

We expect that even when we have lot of process instances (100k+) in the state that the completion and execution should still perform as usual, e.g. 200 job completions per second with 3 partitions.
@ChrisKujawa ChrisKujawa added Hypothesis A thing which worries us and is ready for exploration. Impact: Low The issue has an low impact on the system. Likelihood: Low The issue is really unlikely. Impact: High The issue has an high impact on the system. Likelihood: Medium The issue is not so likely. Contribution: Performability This issue will contribute to build up confidence in performability. and removed Impact: Low The issue has an low impact on the system. Likelihood: Low The issue is really unlikely. labels Oct 27, 2021
@ChrisKujawa ChrisKujawa changed the title Hypothesis: Bigger state should make an impact on Throughput Hypothesis: Bigger state shouldn't make an impact on Throughput Oct 27, 2021
@ChrisKujawa
Copy link
Member Author

https://zeebe-io.github.io/zeebe-chaos/2021/10/29/Throughput-on-big-state

@anumolurahul
Copy link

@Zelldon
https://docs.camunda.io/docs/8.4/components/best-practices/operations/versioning-process-definitions/#dealing-with-long-running-processes
this documentation says not to worry about long running process instances but I am inferring from the chaos test that having long running instances is detrimental to the performance of the cluster. Is the chaos test old/outdated and not relevant anymore or am I reading the chaos test wrong?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Contribution: Performability This issue will contribute to build up confidence in performability. Hypothesis A thing which worries us and is ready for exploration. Impact: High The issue has an high impact on the system. Likelihood: Medium The issue is not so likely.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ChrisKujawa @anumolurahul