From jonathan.gibbons at oracle.com Mon Mar 11 14:09:54 2013 From: jonathan.gibbons at oracle.com (Jonathan Gibbons) Date: Mon, 11 Mar 2013 14:09:54 -0700 Subject: Proposal: Java Microbenchmark Harness (JMH) In-Reply-To: <512631FA.9080205@oracle.com> References: <512631FA.9080205@oracle.com> Message-ID: <513E4822.7070403@oracle.com> This proposal was posted over two weeks ago. If anyone has any comments, please post them by the end of Friday, March 15. -- Jon On 02/21/2013 06:40 AM, Aleksey Shipilev wrote: > Hi, > > I'd like to propose the new tool for inclusion to Codetools Project > within the OpenJDK. Please find the proposal below: > > ----8<--------------------------------------------------------------- > > Tool Name: > Java Microbenchmark Harness (JMH) > > Tool Purpose: > Java harness for building, running, and analysing the nano/micro/macro > benchmarks, written in Java and other languages targeting the JVM. > > Proposed By: > Aleksey Shipilev, Oracle, Java SE Performance team > > Rationale: > Measuring the performance is the fine art, and measuring the performance > on microbenchmarks is double so. There are multiple caveats one should > take a great care of while designing the experiment involving > microbenchmarks. The advanced experience with VM technology is required, > the exposure with particular nits on exact VM is also a plus. > > JMH is designed to aid the development of reliable microbenchmarks. Our > experience shows there is the clear need for the user-friendly way to > build ad-hoc benchmarks for JDK development and performance research. > None of the tools in the wild are meeting all the needs required for > this kind of work. > > Including JMH in the Code Tools project allows us to use HotSpot- and > OpenJDK-specific functionality available only on this platform to get > better support for benchmarking. (Examples are: sun.misc.*, compiler > whitebox testing API, etc.) > > It is also important to have the harness to keep up with the latest > API/ABI changes, available ahead of GA for a new release of JDK. It had > already been proved useful when dealing with JSR166, JSR292, Lambda > performance assessments, and other bleeding edge platform improvements. > > In addition, JMH samples will guide the developers through the general > benchmarking pitfalls, as well as OpenJDK-specific nits, which will > greatly improve the quality of the ad-hoc performance testing in OpenJDK. > > ----8<--------------------------------------------------------------- > > Thanks, > Aleksey. From jonathan.gibbons at oracle.com Mon Mar 25 23:24:27 2013 From: jonathan.gibbons at oracle.com (Jonathan Gibbons) Date: Mon, 25 Mar 2013 23:24:27 -0700 Subject: Proposal: Java Microbenchmark Harness (JMH) In-Reply-To: <513E4822.7070403@oracle.com> References: <512631FA.9080205@oracle.com> <513E4822.7070403@oracle.com> Message-ID: <51513F1B.9090906@oracle.com> In the absence of any discussion, this proposal is accepted. Welcome to Code Tools. -- Jon On 03/11/2013 02:09 PM, Jonathan Gibbons wrote: > This proposal was posted over two weeks ago. > > If anyone has any comments, please post them by the > end of Friday, March 15. > > -- Jon > > > On 02/21/2013 06:40 AM, Aleksey Shipilev wrote: >> Hi, >> >> I'd like to propose the new tool for inclusion to Codetools Project >> within the OpenJDK. Please find the proposal below: >> >> ----8<--------------------------------------------------------------- >> >> Tool Name: >> Java Microbenchmark Harness (JMH) >> >> Tool Purpose: >> Java harness for building, running, and analysing the nano/micro/macro >> benchmarks, written in Java and other languages targeting the JVM. >> >> Proposed By: >> Aleksey Shipilev, Oracle, Java SE Performance team >> >> Rationale: >> Measuring the performance is the fine art, and measuring the performance >> on microbenchmarks is double so. There are multiple caveats one should >> take a great care of while designing the experiment involving >> microbenchmarks. The advanced experience with VM technology is required, >> the exposure with particular nits on exact VM is also a plus. >> >> JMH is designed to aid the development of reliable microbenchmarks. Our >> experience shows there is the clear need for the user-friendly way to >> build ad-hoc benchmarks for JDK development and performance research. >> None of the tools in the wild are meeting all the needs required for >> this kind of work. >> >> Including JMH in the Code Tools project allows us to use HotSpot- and >> OpenJDK-specific functionality available only on this platform to get >> better support for benchmarking. (Examples are: sun.misc.*, compiler >> whitebox testing API, etc.) >> >> It is also important to have the harness to keep up with the latest >> API/ABI changes, available ahead of GA for a new release of JDK. It had >> already been proved useful when dealing with JSR166, JSR292, Lambda >> performance assessments, and other bleeding edge platform improvements. >> >> In addition, JMH samples will guide the developers through the general >> benchmarking pitfalls, as well as OpenJDK-specific nits, which will >> greatly improve the quality of the ad-hoc performance testing in >> OpenJDK. >> >> ----8<--------------------------------------------------------------- >> >> Thanks, >> Aleksey. > From iris.clark at oracle.com Tue Mar 26 10:50:42 2013 From: iris.clark at oracle.com (Iris Clark) Date: Tue, 26 Mar 2013 10:50:42 -0700 (PDT) Subject: CFV: New Code Tools Committer: Aleksey Shipilev Message-ID: <42c04cd6-dcb9-4cad-a9ab-ceabd915dc36@default> Hi! I hereby nominate Aleksey Shipilev to Code Tools Committer. Aleksey is the original author of the Java Microbenchmark Harness (JMH) and continues to be responsible for its development and maintenance. He has identified and made several performance-related contributions to various OpenJDK Projects (e.g. JDK 8, HSX, Lambda) with the assistance of this tool. Votes are due by Tuesday, April 9, 2013 at 19:00 UTC [1]. Only current Code Tools Committers [2] are eligible to vote on this nomination. Votes must be cast in the open by replying to to this mailing list. For Lazy Consensus voting instructions, see [3]. Thanks, Iris Clark [1]: http://www.timeanddate.com/worldclock/fixedtime.html?msg=CFV%3A+New+Code+Tools+Committer+Aleksey+Shipilev&iso=20130409T12&p1=224 [2]: http://openjdk.java.net/census#code-tools [3]: http://openjdk.java.net/projects/#committer-vote From jonathan.gibbons at oracle.com Tue Mar 26 11:06:13 2013 From: jonathan.gibbons at oracle.com (Jonathan Gibbons) Date: Tue, 26 Mar 2013 11:06:13 -0700 Subject: CFV: New Code Tools Committer: Aleksey Shipilev In-Reply-To: <42c04cd6-dcb9-4cad-a9ab-ceabd915dc36@default> References: <42c04cd6-dcb9-4cad-a9ab-ceabd915dc36@default> Message-ID: <5151E395.7050708@oracle.com> Vote: yes On 03/26/2013 10:50 AM, Iris Clark wrote: > Hi! > > I hereby nominate Aleksey Shipilev to Code Tools Committer. > > Aleksey is the original author of the Java Microbenchmark Harness (JMH) and continues to be responsible for its development and maintenance. He has identified and made several performance-related contributions to various OpenJDK Projects (e.g. JDK 8, HSX, Lambda) with the assistance of this tool. > > Votes are due by Tuesday, April 9, 2013 at 19:00 UTC [1]. > > Only current Code Tools Committers [2] are eligible to vote on > this nomination. Votes must be cast in the open by replying to > to this mailing list. > > For Lazy Consensus voting instructions, see [3]. > > Thanks, > Iris Clark > > [1]: http://www.timeanddate.com/worldclock/fixedtime.html?msg=CFV%3A+New+Code+Tools+Committer+Aleksey+Shipilev&iso=20130409T12&p1=224 > [2]: http://openjdk.java.net/census#code-tools > [3]: http://openjdk.java.net/projects/#committer-vote From kevin.looney at oracle.com Tue Mar 26 11:32:24 2013 From: kevin.looney at oracle.com (Kevin Looney) Date: Tue, 26 Mar 2013 11:32:24 -0700 Subject: CFV: New Code Tools Committer: Aleksey Shipilev In-Reply-To: <5151E395.7050708@oracle.com> References: <42c04cd6-dcb9-4cad-a9ab-ceabd915dc36@default> <5151E395.7050708@oracle.com> Message-ID: <5151E9B8.6080605@oracle.com> Vote: yes On 3/26/13 11:06 AM, Jonathan Gibbons wrote: > Vote: yes > > On 03/26/2013 10:50 AM, Iris Clark wrote: >> Hi! >> >> I hereby nominate Aleksey Shipilev to Code Tools Committer. >> >> Aleksey is the original author of the Java Microbenchmark Harness >> (JMH) and continues to be responsible for its development and >> maintenance. He has identified and made several performance-related >> contributions to various OpenJDK Projects (e.g. JDK 8, HSX, Lambda) >> with the assistance of this tool. >> >> Votes are due by Tuesday, April 9, 2013 at 19:00 UTC [1]. >> >> Only current Code Tools Committers [2] are eligible to vote on >> this nomination. Votes must be cast in the open by replying to >> to this mailing list. >> >> For Lazy Consensus voting instructions, see [3]. >> >> Thanks, >> Iris Clark >> >> [1]: >> http://www.timeanddate.com/worldclock/fixedtime.html?msg=CFV%3A+New+Code+Tools+Committer+Aleksey+Shipilev&iso=20130409T12&p1=224 >> [2]: http://openjdk.java.net/census#code-tools >> [3]: http://openjdk.java.net/projects/#committer-vote > -- kevin.looney at oracle.com