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

Posted to dev@phoenix.apache.org by "James Taylor (JIRA)" <ji...@apache.org> on 2018/05/01 18:50:00 UTC

[jira] [Resolved] (PHOENIX-4718) Decrease overhead of tracking aggregate heap size

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

James Taylor resolved PHOENIX-4718.
-----------------------------------
    Resolution: Fixed

> Decrease overhead of tracking aggregate heap size
> -------------------------------------------------
>
>                 Key: PHOENIX-4718
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4718
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: James Taylor
>            Assignee: James Taylor
>            Priority: Major
>             Fix For: 4.14.0, 5.0.0
>
>         Attachments: PHOENIX-4718-4.x-HBase-0.98.patch, PHOENIX-4718.patch, PHOENIX-4718_v2.patch, PHOENIX-4718_v3.patch
>
>
> Since PHOENIX-4148, we track the heap size while aggregation is occurring. This decreased performance of aggregation by ~20%. We really only need to track this for the DistinctValueWithCountServerAggregator (used by DISTINCT COUNT, DISTINCT, PERCENTILE functions, and STDDEV functions). By conditionally tracking, we should be able to bring perf back to what it was before.



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