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

ASF GitHub Bot commented on DRILL-5755:
---------------------------------------

GitHub user ilooner opened a pull request:

    https://github.com/apache/drill/pull/964

    DRILL-5755 Reduced default number of batches kept in memory by TopN

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/ilooner/drill DRILL-5755

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/drill/pull/964.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #964
    
----
commit 80ff848a419b65ae578a382a24971a01d97f2eb0
Author: Timothy Farkas <[email protected]>
Date:   2017-09-21T22:59:58Z

    DRILL-5755 Reduced default number of batches kept in memory by the TopN 
operator.

----


> TOP_N_SORT operator does not free memory while running
> ------------------------------------------------------
>
>                 Key: DRILL-5755
>                 URL: https://issues.apache.org/jira/browse/DRILL-5755
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Execution - Relational Operators
>    Affects Versions: 1.11.0
>            Reporter: Boaz Ben-Zvi
>            Assignee: Timothy Farkas
>            Priority: Blocker
>         Attachments: 2658c253-20b6-db90-362a-139aae4a327e.sys.drill
>
>
>  The TOP_N_SORT operator should keep the top N rows while processing its 
> input, and free the memory used to hold all rows below the top N.
> For example, the following query uses a table with 125M rows:
> {code}
> select row_count, sum(row_count), avg(double_field), max(double_rand), 
> count(float_rand) from dfs.`/data/tmp` group by row_count order by row_count 
> limit 30;
> {code}
> And failed with an OOM when each of the 3 TOP_N_SORT operators was holding 
> about 2.44 GB !! (see attached profile).  It should take far less memory to 
> hold 30 rows !!



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to