[
https://issues.apache.org/jira/browse/IMPALA-7351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16639067#comment-16639067
]
ASF subversion and git services commented on IMPALA-7351:
---------------------------------------------------------
Commit 3fabc2de4771349079bcd9dc8bdcb267f43b2a6b in impala's branch
refs/heads/master from [~bikram.sngh91]
[ https://git-wip-us.apache.org/repos/asf?p=impala.git;h=3fabc2d ]
IMPALA-7351: Improve memory estimates for Kudu Scan Nodes
This patch adds memory estimates for kudu scan nodes based on
empirically derived estimates for the scan's memory consumption
that were added in IMPALA-7096.
Testing:
Modified resource requirements planner test.
Change-Id: If9bb52530271b0bff91311a67d222a2e9fac1229
Reviewed-on: http://gerrit.cloudera.org:8080/11440
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: 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]
