[ 
https://issues.apache.org/jira/browse/PROTON-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16258140#comment-16258140
 ] 

ASF GitHub Bot commented on PROTON-1690:
----------------------------------------

GitHub user franz1981 opened a pull request:

    https://github.com/apache/qpid-proton-j/pull/12

    PROTON-1690 JMH Benchmarks for baseline performance of Message 
encoding/decoding

    It adds a module to perform reliable (and repeatible) benchmarks on a basic 
Message encoding/decoding.
    The benchamarks could be saved in several human readable forms (normal 
text, CSV, JSON etc) and can be run from the IDE (to test immediatly some 
changes in the dev fork/branch) or as a standalone jar.
    It is just the base that could contain future benchmarks on other critical 
parts.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/franz1981/qpid-proton-j msg_jmh_bench

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/qpid-proton-j/pull/12.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #12
    
----
commit 950169d8a2a70778a4e1789aad2cd66d043c7b6f
Author: Francesco Nigro <[email protected]>
Date:   2017-11-18T17:51:31Z

    PROTON-1690 JMH Benchmarks for baseline performance of Message 
encoding/decoding

----


> JMH Benchmarks for baseline performance of Message encoding/decoding
> --------------------------------------------------------------------
>
>                 Key: PROTON-1690
>                 URL: https://issues.apache.org/jira/browse/PROTON-1690
>             Project: Qpid Proton
>          Issue Type: New Feature
>          Components: proton-j
>            Reporter: Francesco Nigro
>            Priority: Minor
>
> Using a standard and reliable tool to quantify the performances of critical 
> components would be useful to measure the effects of any changes in the 
> engine.
> Currently lo standard the facto for such measurements is JMH 
> (http://openjdk.java.net/projects/code-tools/jmh/) hence it is highly 
> desiderable to use it to avoid the JVM to perform un-wanted (ie unrealistic 
> in production uses) optimizations that could trick the results of any 
> handrolled measurements.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to