[ 
https://issues.apache.org/jira/browse/YARN-6610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16129366#comment-16129366
 ] 

Wangda Tan commented on YARN-6610:
----------------------------------

[~templedf],

Thanks for updating patch, I did some test and got some amazing results:
By executing test: {{mvn test 
-Dtest=TestCapacityScheduler#testUserLimitThroughput 
-DRunUserLimitThroughput=true}}

For throughput (higher is better)
1) YARN-3926 w/o the patch: 50505.05
2) trunk: 57142.855
3) 3926 + 6610 (perf): {color:red}606060.6 (!!){color}
4) 3926 + 6610 (006): 46403.71

Since YARN-3926 is rebased to trunk, I did some rebases while doing the test as 
well. The number looks great, I just hope we didn't accidentally introduce some 
issues. I will do some other verifications as well.

> DominantResourceCalculator.getResourceAsValue() dominant param is no longer 
> appropriate
> ---------------------------------------------------------------------------------------
>
>                 Key: YARN-6610
>                 URL: https://issues.apache.org/jira/browse/YARN-6610
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: resourcemanager
>    Affects Versions: YARN-3926
>            Reporter: Daniel Templeton
>            Assignee: Daniel Templeton
>            Priority: Critical
>         Attachments: YARN-6610.001.patch, YARN-6610.YARN-3926.002.patch, 
> YARN-6610.YARN-3926.003.patch, YARN-6610.YARN-3926.004.patch, 
> YARN-6610.YARN-3926.005.patch, YARN-6610.YARN-3926.006.patch, 
> YARN-6610.YARN-3926.perf.patch
>
>
> The {{dominant}} param assumes there are only two resources, i.e. true means 
> to compare the dominant, and false means to compare the subordinate.  Now 
> that there are _n_ resources, this parameter no longer makes sense.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to