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:I believe I can start a lot of timers without impacting the general throughput #31

Open
ChrisKujawa opened this issue Jul 9, 2020 · 1 comment
Open

Hypothesis:I believe I can start a lot of timers without impacting the general throughput #31

ChrisKujawa opened this issue Jul 9, 2020 · 1 comment
Labels
Await Fix Contribution: Availability This issue will contribute to build up confidence in reliability. Contribution: Performability This issue will contribute to build up confidence in performability. Hypothesis A thing which worries us and is ready for exploration. Impact: Low The issue has an low impact on the system. Likelihood: High The likelihood of this issue is really high!

Comments

@ChrisKujawa
Copy link
Member

Hypothesis

I believe I can start a lot of timers without impacting the general throughput.

I expect that the processed records (events/commands) are stable. It might that creating new workflow instances will not work due to back pressure, but the processing should not stop.
@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: High The likelihood of this issue is really high! Contribution: Availability This issue will contribute to build up confidence in reliability. Contribution: Performability This issue will contribute to build up confidence in performability. labels Jul 9, 2020
@ChrisKujawa ChrisKujawa changed the title Hypothesis: I can continuously start timers without impacting my performance Hypothesis:I believe I can start a lot of timers without impacting the general throughput Jul 9, 2020
@ChrisKujawa
Copy link
Member Author

Done in last chaos day https://github.com/zeebe-io/zeebe-chaos/blob/master/chaos-days/2020-07-09/summary.md Found out that the throughput is not stable since processing and timer triggering are coupled. Created camunda/camunda#4931

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

No branches or pull requests
1 participant
@ChrisKujawa