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

Evaluate potential Gatling successors #1087

Closed
kami619 opened this issue Jan 6, 2025 · 0 comments
Closed

Evaluate potential Gatling successors #1087

kami619 opened this issue Jan 6, 2025 · 0 comments
Assignees

Comments

@kami619
Copy link
Contributor

kami619 commented Jan 6, 2025

Evaluate the tool based on the below heuristics,

  • Supported Language - Preferably Java support
  • Support for concurrent execution of scenarios
  • Support for dynamic data injection and ability to control the run based on target objectives
  • Able to generate detailed reports with long tail percentiles for latency, throughput rate, error distribution, latency distribution and time-series graphs with the ability to plot both client-side and server-side errors
    • Bonus points for having native support for Prometheus and/or Grafana visualization.
  • Ability to monitor the performance test run when the load test run is happening.
  • Using a license approved by the CNCF, or a open source friendly license with an exception granted by the CNCF
  • Should be able to integrate with the existing dataset module
  • Should have very close features that can support the existing kcb.sh feature flags
    https://github.com/keycloak/keycloak-benchmark/blob/main/benchmark/src/main/content/bin/kcb.sh#L62-L77
    https://github.com/keycloak/keycloak-benchmark/blob/main/benchmark/src/main/java/org/keycloak/benchmark/Config.java
  • Should supported the SLO/SLI metrics based load tests, this could bring us closer to our long term vision (this goal needs to be discussed with the team in detail)
@kami619 kami619 self-assigned this Jan 6, 2025
@kami619 kami619 changed the title Evaluate https://locust.io/ if it could be the successor of Gatling Evaluate Locust load testing tool, if it could be the successor of Gatling Jan 6, 2025
@mhajas mhajas changed the title Evaluate Locust load testing tool, if it could be the successor of Gatling Evaluate potential Gatling successors Jan 14, 2025
@kami619 kami619 assigned mhajas and unassigned kami619 Jan 20, 2025
@mhajas mhajas closed this as completed Jan 21, 2025
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

2 participants