Kunal Khatua commented on DRILL-6180:

Wouldn't it make sense to have an operator specific option for defining output 
batch size?

A generic option is good to have, but I suspect that we'll go down the same 
road as {{planner.width.max_per_node}} where one-size-fits-all is suboptimal.

> Use System Option "output_batch_size" for External Sort
> -------------------------------------------------------
>                 Key: DRILL-6180
>                 URL: https://issues.apache.org/jira/browse/DRILL-6180
>             Project: Apache Drill
>          Issue Type: Improvement
>          Components: Execution - Flow
>    Affects Versions: 1.12.0
>            Reporter: Padma Penumarthy
>            Assignee: Padma Penumarthy
>            Priority: Critical
>             Fix For: 1.13.0
> External Sort has boot time configuration for output batch size 
> "drill.exec.sort.external.spill.merge_batch_size" which is defaulted to 16M.
> To make batch sizing configuration uniform across all operators, change this 
> to use new system option that is added 
> "drill.exec.memory.operator.output_batch_size". This option has default value 
> of 32M.
> So, what are the implications if default is changed to 32M for external sort ?
> Instead, should we change the output batch size default to 16M for all 
> operators ?

This message was sent by Atlassian JIRA

Reply via email to