[
https://issues.apache.org/jira/browse/GEODE-9176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17332770#comment-17332770
]
Geode Integration commented on GEODE-9176:
------------------------------------------
Seen in [Benchmark_with_security_manager
#153|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/Benchmark_with_security_manager/builds/153].
> Automatically pass benchmark properties to benchmark JVMs
> ---------------------------------------------------------
>
> Key: GEODE-9176
> URL: https://issues.apache.org/jira/browse/GEODE-9176
> Project: Geode
> Issue Type: Improvement
> Components: benchmarks
> Reporter: Dan Smith
> Assignee: Dan Smith
> Priority: Major
> Labels: pull-request-available
>
> The geode-benchmarks currently have some hard coded system properties that
> can be used to change the behavior of the tests. Each property is copied by
> hand the build.gradle file.
> We should not need to name each property in build.gradle file if the
> properties use a consistent naming convention. In addition, we can dump out
> all of the properties that were set with a benchmark to keep track of what
> was different in that run.
> Finally, it's often helpful when debugging to automatically set system
> properties on test JVMs, for example to change geode behavior. By using a
> naming convention we can also automatically pass properties to the benchmark
> JVMs.
> To accomplish this, all existing properties will be renamed to start with
> "benchmark." These properties can be passed as gradle flags. For example
> {code}
> ./gradlew benchmark -Pbenchmark.withThreads=10)
> {code}
> Properties that start with "benchmark.system.ROLE." will be set as system
> properties in the test JVMs.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
