[GitHub] [geode-benchmarks] WireBaron opened pull request #7: GEODE-6086: Adding a tool to allow command line analysis of test runs

["WireBaron (GitHub)" <gi...@apache.org>]

This change adds the analyzeRun gradle target, which, when passed a baseline
result directory and test result directory via --args, will analyze the output
and report the variation of the test from the baseline.


Sample output: 
```
MacBook-Pro-2:geode-performance browe$ ./gradlew analyzeRun --args "/Users/browe/project/geode-performance/geode-benchmarks/output2 /Users/browe/project/geode-performance/geode-benchmarks/output"

> Task :harness:analyzeRun
Running analyzer
Comparing test result at /Users/browe/project/geode-performance/geode-benchmarks/output2 to baseline at /Users/browe/project/geode-performance/geode-benchmarks/output
-- PartitionedPutBenchmark --
average ops/second
Result: 47386.93220338983
Baseline: 46237.745762711864
Relative performance: 1.0248538595842343

99th percentile latency
Result: 292.85714285714283
Baseline: 294.11764705882354
Relative performance: 0.9957142857142857
```

Two remaining pain points I'd like to address:
1. When adding a benchmark it would be easier to use roles rather than node names
2. It would also be nice to reference the benchmark classes directly in the analyzer (to get their output directories), but that dependency goes the wrong way.

[ Full content available at: https://github.com/apache/geode-benchmarks/pull/7 ]
This message was relayed via gitbox.apache.org for notifications@geode.apache.org

[GitHub] [geode-benchmarks] WireBaron closed pull request #7: GEODE-6086: Adding a tool to allow command line analysis of test runs

["WireBaron (GitHub)" <gi...@apache.org>]

[ pull request closed by WireBaron ]

[ Full content available at: https://github.com/apache/geode-benchmarks/pull/7 ]
This message was relayed via gitbox.apache.org for notifications@geode.apache.org