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 overhead tests to specify a warm-up period #3687

Closed
breedx-splk opened this issue Jul 27, 2021 · 0 comments · Fixed by #3815
Closed

Allow overhead tests to specify a warm-up period #3687

breedx-splk opened this issue Jul 27, 2021 · 0 comments · Fixed by #3815
Assignees
Labels
enhancement New feature or request

Comments

@breedx-splk
Copy link
Contributor

In #3627, it was noted that we may wish to have some tests run after a warm-up phase. That is, we don't want to actually start the measurements (with JFR) until after some warm-up cycle so that the jit compilation has had a chance to do its thing and the app has reached more of a steady-state.

As noted in #3627, there are pros and cons of doing this. On one hand, will miss the overhead introduced by the agent during startup, but for many users (especially those with long-running enterprise JVM applications) they may only care about steady-state overhead.

We should modify the overhead test configuration to allow for an optional warm-up cycle, specified in seconds, during which a moderate amount of traffic should be generated. Only after the startup has completed should the relevant measurements begin. With JFR, this can be accomplished with the delay parameter (dynamically configured on the commandline via system props).

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

Successfully merging a pull request may close this issue.

1 participant