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

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

Github user paul-rogers commented on a diff in the pull request:

    https://github.com/apache/drill/pull/860#discussion_r128129092
  
    --- Diff: 
exec/java-exec/src/main/java/org/apache/drill/exec/physical/impl/xsort/managed/PriorityQueueCopierWrapper.java
 ---
    @@ -100,10 +102,12 @@ private PriorityQueueCopier 
newCopier(VectorAccessible batch) {
        * @param batchGroupList
        * @param outputContainer
        * @param targetRecordCount
    +   * @param allocHelper
        * @return
        */
    -  public BatchMerger startMerge(BatchSchema schema, List<? extends 
BatchGroup> batchGroupList, VectorContainer outputContainer, int 
targetRecordCount) {
    -    return new BatchMerger(this, schema, batchGroupList, outputContainer, 
targetRecordCount);
    +  public BatchMerger startMerge(BatchSchema schema, List<? extends 
BatchGroup> batchGroupList,
    --- End diff --
    
    Would probably do it that way if either a) it wasn't test code, or b) the 
allocation thing was not temporary.
    
    The sort code probably should actually create a vector allocator so we test 
what we ship. But, haven't got to that step yet.
    
    Also, hoping that the vector allocator (and sizer) disappear into a larger 
form of batch metadata.


> Rollup of External Sort memory management fixes
> -----------------------------------------------
>
>                 Key: DRILL-5601
>                 URL: https://issues.apache.org/jira/browse/DRILL-5601
>             Project: Apache Drill
>          Issue Type: Task
>    Affects Versions: 1.11.0
>            Reporter: Paul Rogers
>            Assignee: Paul Rogers
>             Fix For: 1.12.0
>
>
> Rollup of a set of specific JIRA entries that all relate to the very 
> difficult problem of managing memory within Drill in order for the external 
> sort to stay within a memory budget. In general, the fixes relate to better 
> estimating memory used by the three ways that Drill allocates vector memory 
> (see DRILL-5522) and to predicting the size of vectors that the sort will 
> create, to avoid repeated realloc-copy cycles (see DRILL-5594).



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

Reply via email to