[
https://issues.apache.org/jira/browse/CASSANDRA-16371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Semb Wever updated CASSANDRA-16371:
-------------------------------------------
Description:
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).
was:
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 difficult (and behave under saturation), and when jmh
classes are broken (there are no unit tests on these benchmark tests).
> 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
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
