You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Dong Lin (Jira)" <ji...@apache.org> on 2023/03/10 07:37:00 UTC

[jira] [Resolved] (FLINK-29825) Improve benchmark stability

     [ https://issues.apache.org/jira/browse/FLINK-29825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dong Lin resolved FLINK-29825.
------------------------------
    Resolution: Fixed

> Improve benchmark stability
> ---------------------------
>
>                 Key: FLINK-29825
>                 URL: https://issues.apache.org/jira/browse/FLINK-29825
>             Project: Flink
>          Issue Type: Improvement
>          Components: Benchmarks
>    Affects Versions: 1.17.0
>            Reporter: Yanfei Lei
>            Assignee: Yanfei Lei
>            Priority: Minor
>              Labels: pull-request-available
>
> Currently, regressions are detected by a simple script which may have false positives and false negatives, especially for benchmarks with small absolute values, small value changes would cause large percentage changes. see [here|https://github.com/apache/flink-benchmarks/blob/master/regression_report.py#L132-L136] for details.
> And all benchmarks are executed on one physical machine, it might happen that hardware issues affect performance, like "[FLINK-18614] Performance regression 2020.07.13".
>  
> This ticket aims to improve the precision and recall of the regression-check script.
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)