You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Chesnay Schepler (JIRA)" <ji...@apache.org> on 2018/08/29 07:11:00 UTC

[jira] [Updated] (FLINK-10236) Reduce histogram percentile/quantile retrieval overhead

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

Chesnay Schepler updated FLINK-10236:
-------------------------------------
    Issue Type: Sub-task  (was: Improvement)
        Parent: FLINK-10241

> Reduce histogram percentile/quantile retrieval overhead
> -------------------------------------------------------
>
>                 Key: FLINK-10236
>                 URL: https://issues.apache.org/jira/browse/FLINK-10236
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Metrics
>    Affects Versions: 1.5.0, 1.5.1, 1.5.2, 1.5.3, 1.6.0, 1.7.0
>            Reporter: Nico Kruber
>            Assignee: Nico Kruber
>            Priority: Major
>
> Most of our metrics reporters for histograms always report multiple quantiles: 0.5, 0.75, 0.90, 0.95, 0.98, 0.99, and 0.999.
> This is retrieved from {{HistogramStatistics}}/{{DescriptiveStatisticsHistogramStatistics}} but we do not have any optimisation for retrieving this many percentiles though and the plain use of {{DescriptiveStatistics#getPercentile}} has some constant overhead that could be avoided over multiple executions using {{Percentile#setData(double[])}} to cache the current data set of the snapshot.
> In addition, min, max, mean, and standard deviation also each iterate over the array which could be done a single time.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)