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

Allow running performance test server and simulations separately #3514

Merged
merged 4 commits into from
Feb 12, 2024

Conversation

kciesielski
Copy link
Member

This PR adds some flexibility in the perfTests module. So far it was only possible to run a "test suite" with specified servers and simulations. Server list will now become optional, which allows running a profiled server separately:

perfTests/runMain sttp.tapir.perf.apis.ServerRunner netty.cats.TapirMulti
// in a separate sbt session:
perfTest/Test/runMain sttp.tapir.perf.PerfTestSuiteRunner -m PostBytes,PostLongBytes -d 25

The perfTests/runMain task forks a JVM with

javaOptions += "-XX:StartFlightRecording=filename=recording.jfr,dumponexit=true,duration=120s"

@kciesielski kciesielski marked this pull request as ready for review February 12, 2024 12:50
@kciesielski kciesielski requested a review from adamw February 12, 2024 12:50
@adamw adamw merged commit 26b333b into master Feb 12, 2024
28 checks passed
@adamw adamw deleted the perf-run-profile branch February 12, 2024 13:04
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

Successfully merging this pull request may close these issues.

2 participants