Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Azure Trace for Packing 2020 normalized resources #20

Open
a-papadopoulos opened this issue Apr 1, 2022 · 0 comments
Open

Azure Trace for Packing 2020 normalized resources #20

a-papadopoulos opened this issue Apr 1, 2022 · 0 comments

Comments

@a-papadopoulos
Copy link

a-papadopoulos commented Apr 1, 2022

I'm a bit puzzled by what looks like an inconsistency in the vmType table. I understand resources are given as ratio of total machine capacity, instead of the absolute number, and unless I've missed something, there is no way of obtaining the capacities of any given machineId.

The problem is that some (in fact, many) resources seem to be inconsistent with each other. For example, if I look at the 'core' resources of rows 1,2,111,112,248,249, I have the following table:

'core' 'vmTypeId': 0 'vmTypeId': 1
'machineId': 0 0.020833333333333332 0.020833333333333332
'machineId': 1 0.010416666666666666 0.010416666666666666
'machineId': 2 0.004583333333333333 0.0175

I would expect that the ratio between the 'core' resources for two vm types be the same for any machine type, since presumably, only the denominator of those numbers changes (corresponding to the total machine capacity). But here, the machine with 'machineId' = 2 breaks this invariant.

Does this mean that the resources for a vm type are actually not constant, and depend on the machine type? Or am I missing something?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant