[
https://issues.apache.org/jira/browse/IMPALA-7351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16664412#comment-16664412
]
ASF subversion and git services commented on IMPALA-7351:
---------------------------------------------------------
Commit 8cbec20ea4f1399fce14018d30050d4b7ee501bc in impala's branch
refs/heads/master from [~bikram.sngh91]
[ https://git-wip-us.apache.org/repos/asf?p=impala.git;h=8cbec20 ]
IMPALA-7351: Add estimates to Exchange node
Added rough estimates for exchange node and a justification of the
method in the in-line comments.
Testing:
Updated Planner tests.
Change-Id: I5b577f9511abc48b992e814d50bba4959f23f7fd
Reviewed-on: http://gerrit.cloudera.org:8080/11692
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> Add memory estimates for plan nodes and sinks with missing estimates
> --------------------------------------------------------------------
>
> Key: IMPALA-7351
> URL: https://issues.apache.org/jira/browse/IMPALA-7351
> Project: IMPALA
> Issue Type: Sub-task
> Components: Frontend
> Reporter: Tim Armstrong
> Assignee: Bikramjeet Vig
> Priority: Major
> Labels: admission-control, resource-management
>
> Many plan nodes and sinks, e.g. KuduScanNode, KuduTableSink, ExchangeNode,
> etc are missing memory estimates entirely.
> We should add a basic estimate for all these cases based on experiments and
> data from real workloads. In some cases 0 may be the right estimate (e.g. for
> streaming nodes like SelectNode that just pass through data) but we should
> remove TODOs and document the reasoning in those cases.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
