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

ASF GitHub Bot commented on GROOVY-12735:
-----------------------------------------

github-actions[bot] commented on PR #3271:
URL: https://github.com/apache/groovy/pull/3271#issuecomment-6721451587

   ### JMH summary — indy (commit `6175d69`)
   
   Speedup vs trailing 90-day baseline on gh-pages. Higher = faster.
   `1.00` = in line with history. Per-benchmark ratio, geomean within group.
   Time-per-op units inverted so direction is consistent. The *calibrated*
   column divides out this runner's speed vs the baseline hardware, as
   measured by Groovy-independent pure-Java ruler benchmarks.
   
   | Group  | Speedup | Calibrated | n |
   |--------|---------|------------|---|
   | bench | _no overlap with baseline_ | — | 0 |
   | core | 2.400 × | 2.817 × | 39 |
   | grails | 1.350 × | 1.152 × | 44 |
   
   No benchmark is ≥1.5× slower than its 90-day baseline.
   
   > ⚠️ Runner speed differs ≥15% from the historical baseline hardware for: 
core-hz, grails-ez. Raw speedups are not meaningful for those parts — use the 
calibrated column.
   
   <sub>Runner calibration (this run vs baseline hardware): core-hz 0.85× (3 
rulers) · grails-ez 1.17× (3 rulers)</sub>
   
   <sub>Baseline: <code>dev/bench/jmh/&lt;part&gt;/indy/data.js</code> on 
gh-pages, trailing 90 days. <a 
href="https://apache.github.io/groovy/dev/bench/jmh/summary.html";>Daily 
dashboard</a> · <a 
href="https://apache.github.io/groovy/dev/bench/jmh/";>Per-suite raw 
data</a></sub>
   
   <!

> Bump jline to 4.5.0
> -------------------
>
>                 Key: GROOVY-12735
>                 URL: https://issues.apache.org/jira/browse/GROOVY-12735
>             Project: Groovy
>          Issue Type: Dependency upgrade
>            Reporter: Daniel Sun
>            Priority: Major
>




--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to