We do have support for running micro benchmarks with jmh - see the
geode-benchmarks project. But we don't have anything to watch and fail the
build if the performance gets worse. That may be kinda hard to do since
we're running on shared infrastructure.
-Dan
On Thu, Feb 9, 2017 at 6:13 PM,
It was added to identify performance issues sooner than later...The test
run queries for multiple times so that, jvm hot-spot is kicked-in and
stabilized...
You are right, functional-testing is not the right place for this...
We may need to think about performance test framework/category for
I just had a precheckin fail in BaseLineAndCompareQueryPerfJUnitTest. I'm
not sure a junit test is really a good place for perf testing like this.
Between JVM optimizing at runtime and possibility for machine CPU
pollution, I'm surprised we haven't seen this fail before. Just wanted to
mention
