[ https://issues.apache.org/jira/browse/YARN-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karthik Kambatla updated YARN-23:
---------------------------------
Description:
In FS, FSQueueSchedulable#updateDemand() limits the demand to maxTasks only after iterating
though all the pools and computing the final demand.
By checking if the demand has reached maxTasks in every iteration, we can avoid redundant
work, at the expense of one condition check every iteration.
was:
In FS, PoolSchedulable#updateDemand() limits the demand to maxTasks only after iterating though
all the pools and computing the final demand.
By checking if the demand has reached maxTasks in every iteration, we can avoid redundant
work, at the expense of one condition check every iteration.
Summary: FairScheduler: FSQueueSchedulable#updateDemand() - potential redundant aggregation
(was: FairScheduler: PoolSchedulable#updateDemand() - potential redundant aggregation)
> FairScheduler: FSQueueSchedulable#updateDemand() - potential redundant aggregation
> ----------------------------------------------------------------------------------
>
> Key: YARN-23
> URL: https://issues.apache.org/jira/browse/YARN-23
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: scheduler
> Affects Versions: 2.1.0-alpha
> Reporter: Karthik Kambatla
> Assignee: Karthik Kambatla
> Attachments: trunk-MR-4518.patch, trunk-MR-4518.patch, YARN-23.patch
>
>
> In FS, FSQueueSchedulable#updateDemand() limits the demand to maxTasks only after iterating
though all the pools and computing the final demand.
> By checking if the demand has reached maxTasks in every iteration, we can avoid redundant
work, at the expense of one condition check every iteration.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
|