Azure / Azure/AzurePublicDataset

Azure Trace for Packing 2020 normalized resources

Open
#20 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Jupyter Notebook
Stars
1.2k
Forks
185
PR merge metrics
No merged PRs in 30d

Description

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?

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.