[
https://issues.apache.org/jira/browse/IMPALA-11604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17616834#comment-17616834
]
ASF subversion and git services commented on IMPALA-11604:
----------------------------------------------------------
Commit 1d62bddb84753a040a46687391d9c797d849bd0e in impala's branch
refs/heads/master from wzhou-code
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=1d62bddb8 ]
IMPALA-11617: Pool service should be made aware of processing cost limit
IMPALA-11604 enables the planner to compute CPU usage for certain
queries and to select suitable executor groups to run. The CPU usage is
expressed as the total amount of data to be processed per query.
This patch added the processing cost limit, which is the total amount of
data that each executor group can handle, to the pool service.
Testing:
- Passed core run.
- Verified that processing costs were shown on the admission and
metrics pages of the Impala debug web server.
Change-Id: I9bd2a7284eda47a969ef91e4be19f96d2af53449
Reviewed-on: http://gerrit.cloudera.org:8080/19121
Reviewed-by: Qifan Chen <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> Planner changes for CPU usage
> -----------------------------
>
> Key: IMPALA-11604
> URL: https://issues.apache.org/jira/browse/IMPALA-11604
> Project: IMPALA
> Issue Type: Improvement
> Reporter: Qifan Chen
> Assignee: Qifan Chen
> Priority: Major
>
> Plan scaling based on estimated peak memory has been enabled in
> IMPALA-10992. However, it is sometime desirable to consider CPU-usage (such
> as the number of data processed) as a scaling factor.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
