chore(benchmarks): add more starters per default #4288
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
npepinpe
approved these changes
Apr 16, 2020
|
Yes correct. Actually here seems a commit missing where I adjusted the makefil. I will add this |
To improve our test coverage I added a simple starter and a timer starter. The simple one contains just start event and end event. It is quite interesting to see how the latency behaves on these instances. The timer starter contains a workflow with a timer set to PT1S. Per default we will start all of them to have high load and test that this can be handled by the brokers.
npepinpe
reviewed
Apr 22, 2020
| sed -i "s/default/$namespace/g" Makefile | ||
| sed -i "s/default/$namespace/g" worker.yaml | ||
| sed -i "s/default/$namespace/g" starter.yaml | ||
| sed -i "s/default/$namespace/g" Makefile starter.yaml timer.yaml simpleStarter.yaml worker.yaml |
There was a problem hiding this comment.
Didn't know you could do that 🤔
There was a problem hiding this comment.
Me2 😆 found out accidentally 😄
npepinpe
approved these changes
Apr 22, 2020
|
bors r+ |
zeebe-bors bot
added a commit
that referenced
this pull request
Apr 22, 2020
4288: chore(benchmarks): add more starters per default r=Zelldon a=Zelldon ## Description To improve our test coverage I added a simple starter and a timer starter. The simple one contains just start event and end event. It is quite interesting to see how the latency behaves on these instances and to just introduce some more load to the broker. The timer starter contains a workflow with a timer set to PT1S. Per default we will start all of them to have high load and test that this can be handled by the brokers without any problems.  ## Further I want to add later also workflow with contain message catch events and a pod which just publishes messages. <!-- Please explain the changes you made here. --> <!-- Which issues are closed by this PR or are related --> # Co-authored-by: Christopher Zell <zelldon91@googlemail.com>
Build failed |
|
bors r+ |
zeebe-bors bot
added a commit
that referenced
this pull request
Apr 23, 2020
4288: chore(benchmarks): add more starters per default r=Zelldon a=Zelldon ## Description To improve our test coverage I added a simple starter and a timer starter. The simple one contains just start event and end event. It is quite interesting to see how the latency behaves on these instances and to just introduce some more load to the broker. The timer starter contains a workflow with a timer set to PT1S. Per default we will start all of them to have high load and test that this can be handled by the brokers without any problems.  ## Further I want to add later also workflow with contain message catch events and a pod which just publishes messages. <!-- Please explain the changes you made here. --> <!-- Which issues are closed by this PR or are related --> # Co-authored-by: Christopher Zell <zelldon91@googlemail.com>
Build failed |
|
bors r+... |
zeebe-bors bot
added a commit
that referenced
this pull request
Apr 23, 2020
4288: chore(benchmarks): add more starters per default r=Zelldon a=Zelldon ## Description To improve our test coverage I added a simple starter and a timer starter. The simple one contains just start event and end event. It is quite interesting to see how the latency behaves on these instances and to just introduce some more load to the broker. The timer starter contains a workflow with a timer set to PT1S. Per default we will start all of them to have high load and test that this can be handled by the brokers without any problems.  ## Further I want to add later also workflow with contain message catch events and a pod which just publishes messages. <!-- Please explain the changes you made here. --> <!-- Which issues are closed by this PR or are related --> # Co-authored-by: Christopher Zell <zelldon91@googlemail.com>
Build failed |
github-merge-queue bot
pushed a commit
that referenced
this pull request
Apr 16, 2024
…4288) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: Houssain Barouni <146710021+houssain-barouni@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
To improve our test coverage I added a simple starter and a timer starter. The simple one contains just start event and end event. It is quite interesting to see how the latency behaves on these instances and to just introduce some more load to the broker.
The timer starter contains a workflow with a timer set to PT1S. Per default we will start all of them
to have high load and test that this can be handled by the brokers without any problems.
Further
I want to add later also workflow with contain message catch events and a pod which just publishes messages.
Pull Request Checklist
mvn clean install -DskipTestslocally before committing