[
https://issues.apache.org/jira/browse/PROTON-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16278280#comment-16278280
]
ASF GitHub Bot commented on PROTON-1690:
----------------------------------------
Github user franz1981 commented on the issue:
https://github.com/apache/qpid-proton-j/pull/12
Thanks @gemmellr I've tried to fix the PR using your good advices :+1:
And I ask your and @tabish121 help to check if the content of each
benchmark respect somehow what kind of baseline you're interested for each case
eg I've created a `StringsBenchmark` that encode/decode 3 strings at time but
maybe you're more interested in having the benchamark to measure just 1 string
encoded/decoded with several different meaningful lengths (8,36,128?) as
parameters
> 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]
