[
https://issues.apache.org/jira/browse/YARN-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13729724#comment-13729724
]
Arun C Murthy commented on YARN-1024:
-------------------------------------
bq. If I were to package my simulator and give it to other people on other
clusters, it would still be true that it spins one CPU. Its runtime, however,
would vary depending on the horsepower.
I don't see the conflict.
If you don't care about predictable runtime, you could still say I want to run
on 1 virtual-core. By the above non-requirement on predictability, whether it's
1 (virtual) core out of 16 physical cores or 1024 virtual cores is immaterial,
isn't it? And yes, you still get only 1 physical core since the virtual core is
mapped to a single physical core.
The point about specifying a virtual core is that you get predictable
performance when you migrate your application between clusters and other
goodness.
What am I missing here?
> Define a virtual core unambigiously
> -----------------------------------
>
> Key: YARN-1024
> URL: https://issues.apache.org/jira/browse/YARN-1024
> Project: Hadoop YARN
> Issue Type: Improvement
> Reporter: Arun C Murthy
> Assignee: Arun C Murthy
>
> We need to clearly define the meaning of a virtual core unambiguously so that
> it's easy to migrate applications between clusters.
> For e.g. here is Amazon EC2 definition of ECU:
> http://aws.amazon.com/ec2/faqs/#What_is_an_EC2_Compute_Unit_and_why_did_you_introduce_it
> Essentially we need to clearly define a YARN Virtual Core (YVC).
> Equivalently, we can use ECU itself: *One EC2 Compute Unit provides the
> equivalent CPU capacity of a 1.0-1.2 GHz 2007 Opteron or 2007 Xeon processor.*
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
