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

Include JVM Arguments in the Workload Key #27

Open
eostermueller opened this issue Mar 14, 2020 · 0 comments
Open

Include JVM Arguments in the Workload Key #27

eostermueller opened this issue Mar 14, 2020 · 0 comments
Labels
enhancement New feature or request

Comments

@eostermueller
Copy link
Owner

The "Workload Key" is a json blob of text that defines the current code that's running.
With a little work, JVM parameters (like gc configuration, classloader configuration, other -D parameters) could be added.

When a "Workload Key" contained JVM parameters, there are some important considerations:

  • JVM would need to be restarted, which can take several seconds
  • Must detect JVM parameters not supported by the "currently configured" JDK. For example, if you've specified G1 GC parameters in a 1.6jdk...the JVM might not even start.
  • Which JVMs will users be able to specify parameters for? Of course, the SUT would be the highest priority. But what about JVM running H2? What about the JVM running wiremock?
@eostermueller eostermueller added the enhancement New feature or request label Mar 14, 2020
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

No branches or pull requests

1 participant