Hi everyone,
Just to update you all, the framework for running JMH benchmarks is almost ready to be merged into Jenkins Test Harness. Please see this <https://github.com/jenkinsci/jenkins-test-harness/pull/135> pull request. There is also a pull request to the plugin-pom <https://github.com/jenkinsci/plugin-pom/pull/206> for running benchmarks through a Maven profile. For ease of use in plugins hosted on ci.jenkins.io, there is also a work-in-progress pull request <https://github.com/jenkins-infra/pipeline-library/pull/91> to add support for running them as a pipeline step to Jenkins’ pipeline library. I would love to hear your feedback and comments. Thanks Abhyudaya Sharma GitHub: AbhyudayaSharma <https://github.com/AbhyudayaSharma/> From: [email protected] <[email protected]> On Behalf Of Oleg Nenashev Sent: Tuesday, June 4, 2019 1:20 PM To: Jenkins Developers <[email protected]> Subject: Re: Benchmarking Jenkins using Java Microbenchmark Harness (JMH) Hi all, You can find the video recording of the demo here: https://www.youtube.com/watch?v=sr28UADG1AE There is also an ongoing pull request to make it a part of Jenkins Test Harness: https://github.com/jenkinsci/jenkins-test-harness/pull/135 Best regards, Oleg On Thursday, May 30, 2019 at 6:44:38 PM UTC+2, Matt Sicker wrote: I'm +1 in using JMH and exploring benchmarks of various functionality. Seems like a good idea, especially with all the reinvented database functionality implicit in Jenkins and plugins. On Thu, May 30, 2019 at 12:57 AM Oleg Nenashev <[email protected] <javascript:> > wrote: > > Hi all, > > Just to facilitate this thread, I am +1 regarding having micro-benchmarking > support in Jenkins Test Harness. There are many stories related to > performance degradation in Jenkins, and having a framework could help us to > have some checks for the critical functionality like permission checks. The > end goal of the project is to improve Role Strategy performance (which is far > from perfect now), but it would be great if we could reuse the framework in > other components. > > Tomorrow at 7am UTC we will be doing a recorded demo of the current framework > state, and everybody is welcome to join. > > Best regards, > Oleg > > On Tuesday, May 28, 2019 at 8:20:14 AM UTC+2, [email protected] > <mailto:[email protected]> wrote: >> >> Hi everyone, >> >> As a part of this year's Google Summer of Code, I have been working on a >> framework for allowing Java Microbenchmark Harness (JMH) benchmarks to be >> run with Jenkins. The basic framework was implemented in the Role Strategy >> Plugin through this pull request: >> https://github.com/jenkinsci/role-strategy-plugin/pull/63 . For each >> benchmark, a temporary Jenkins instance is created, similar to how >> JenkinsRule from Jenkins Test Harness does it. The benchmarks are run >> through a unit test which allows them to be integrated with the normal pull >> request builds (if required). Apart from configuring the Jenkins instance >> for test using Java code, I've also added support for easily configuring the >> instance by YAML files using Jenkins Configuration as Code. The benchmark >> reports are generated as JSON files which are compatible with the jmh-report >> plugin. I have implemented a couple of benchmarks for the Role Strategy >> Plugin which can be seen in the Role Strategy Plugin GitHub repository. I >> have attached screenshots of these results as visualized by the jmh-report >> plugin. To make the framework easier to use, I'm also working on running the >> benchmarks through a Maven profile. >> >> To make it available to the rest of the community, I would like to propose >> to make it either a part of Jenkins Test Harness or a part of new library so >> it can be used by other plugins and perhaps by Jenkins core itself. I would >> to love to hear your feedback, comments and suggestions. It would be even >> better if you could join the project's weekly meetings (Tuesdays and Fridays >> at 7:00 AM UTC) and help us improve this framework. >> >> Thanks >> Abhyudaya >> GitHub: AbhyudayaSharma >> >> > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] <javascript:> . > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/09147b86-6565-4b83-a4f8-3fbf48baa6cf%40googlegroups.com. > > For more options, visit https://groups.google.com/d/optout. -- Matt Sicker Senior Software Engineer, CloudBees -- You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/W1jrwTEFnz0/unsubscribe. To unsubscribe from this group and all its topics, send an email to [email protected] <mailto:[email protected]> . To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/676323d7-7d32-43be-9003-d0d8eab9e02e%40googlegroups.com <https://groups.google.com/d/msgid/jenkinsci-dev/676323d7-7d32-43be-9003-d0d8eab9e02e%40googlegroups.com?utm_medium=email&utm_source=footer> . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/00d901d51f80%24359a0960%24a0ce1c20%24%40gmail.com. For more options, visit https://groups.google.com/d/optout.
