[
https://issues.apache.org/jira/browse/CASSANDRA-16371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17256450#comment-17256450
]
Michael Semb Wever commented on CASSANDRA-16371:
------------------------------------------------
Another example, now with multiple build results available:
https://ci-cassandra.apache.org/job/Cassandra-devbranch-microbench/7/jdk=jdk_1.8_latest,label=cassandra/jmh-run-report/
(screenshot attached)
> JMH Reports in ci-cassandra.apache.org
> --------------------------------------
>
> Key: CASSANDRA-16371
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16371
> Project: Cassandra
> Issue Type: Task
> Components: CI, Test/benchmark
> Reporter: Michael Semb Wever
> Assignee: Michael Semb Wever
> Priority: Low
> Attachments: JMH #1 [Jenkins .png, JMH #7 [Jenkins .png
>
>
> Enable the jenkins [jmh reporting
> plugin|https://plugins.jenkins.io/jmh-report/] and add a jenkins job to run
> the `ant microbench` target.
> Patches
> - cassandra-builds:
> https://github.com/apache/cassandra-builds/compare/trunk...thelastpickle:mck/jenkins-microbench
> - cassandra:
> https://github.com/apache/cassandra/compare/trunk...thelastpickle:mck/trunk_jmh_report
> Example results are:
> - CI JMH report:
> https://ci-cassandra.apache.org/job/Cassandra-devbranch-microbench/jdk=jdk_11_latest,label=cassandra/1/jmh-run-report/
> (screenshot attached)
> The value of these reports is limited, with different hardware jenkins agents
> and two executors on each agent. But visibility from the reports shows what
> is possible, how agents are different (and behave under saturation), and most
> importantly when jmh classes are broken (there are no unit tests on these
> benchmark tests).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
