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

Performance benchmark as a CI step #517

Open
malaskowski opened this issue Jun 15, 2020 · 0 comments
Open

Performance benchmark as a CI step #517

malaskowski opened this issue Jun 15, 2020 · 0 comments

Comments

@malaskowski
Copy link
Member

Is your feature request related to a problem? Please describe.
Currently unit, integration and functional tests are triggered during the CI build on Azure DevOps.
Impact of new features is not monitored automatically. It would be very beneficial, to setup some performance benchmark as a part of the pipeline that will run simple performance check and compare the results agains some threshold.

Describe the solution you'd like
Performance benchmark is a part of the build pipeline.
The very basic idea would be to run the knotx-starterkit as a docker container and use some load generator (this looks quite promising) and gather results.
Additionally there should be threshold (KPI) set that will fail the build if KPI is not met.

Describe alternatives you've considered
There are a few alternatives:

  • instead of knoxt-starterkit use some knotx-examples to cover more complex scenarios in tests
  • performance checks are scheduled nightly not as parto fo the build pipeline

Additional context
As part of this task, some Azure DevOps RnD should be done, to check if that's possible to run such performance benchmark during the pipeline and to check if any additional servers to run Knot.x are required or not.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant