You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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:
The text was updated successfully, but these errors were encountered: