[
https://issues.apache.org/jira/browse/TINKERPOP-1016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15074454#comment-15074454
]
Ted Wilmes commented on TINKERPOP-1016:
---------------------------------------
[~spmallette] I've been getting up to speed on JMH. JMH folks recommend that
an uber jar of your project be created. JMH then instruments it on the fly and
the tests are run. It looks like the cleanest way to do this would be to
isolate the new performance tests in their own module. That module would in
turn have the JMH and tinkerpop dependencies and create a standalone uber jar
that would then be exercised by JMH. Alternatively we could possibly include
conditional uber jar creation within the existing modules, gremlin-core, etc.
If we did that, we'd end up having to update each module where we wanted to add
perf tests. That seemed more invasive and error prone so that's why I was
leaning towards creating a self contained performance module. I was curious
what your thoughts were though.
> Replace junit-benchmarks with JMH
> ---------------------------------
>
> Key: TINKERPOP-1016
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1016
> Project: TinkerPop
> Issue Type: Improvement
> Components: test-suite
> Affects Versions: 3.1.0-incubating
> Reporter: Ted Wilmes
> Assignee: Ted Wilmes
> Priority: Minor
>
> Replace junit-benchmark with JMH. This includes the following tasks:
> * Evaluate which existing benchmarks should be kept and port them to JMH.
> * Add an initial JMH benchmark for TINKERPOP-957
> * See if we can trigger perf tests with the same scheme that is currently
> used {noformat}mvn verify -DskipPerformanceTests=true/false{noformat}
> * Write developer docs that outline our initial performance testing approach.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
