Azure-docs: Better Explanation of Virtual Machine Size "Tags"

[rlisnoff]

I don't think there's any central location that these "tags", as I'm calling them, are explained.
By tags I mean the trailing letters on a VM's size that seem to denote some aspect about that size that sets it apart from the non-tagged version. Examples include: Standard_M32ts, Standard_M32ls, etc.

I understand the "s" at the end denotes Premium Storage, and "r" seems to denote RDMA capability, but others I have no inkling as to what they mean. A table relating each tag to a meaning would help very much.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 58fe6a40-0b95-f1ed-db11-7a49d4a97ecf
• Version Independent ID: 54269236-da55-a1cd-01df-79a0458d9ac9
• Content: Windows Azure VM sizes - Memory
• Content Source: articles/virtual-machines/windows/sizes-memory.md
• Service: virtual-machines-windows
• GitHub Login: @jonbeck7
• Microsoft Alias: jonbeck

[mimckitt]

Thanks for the feedback! We are currently investigating and will update you shortly.

[Karishma-Tiwari-MSFT]

@rlisnoff Appreciate your feedback.
I have assigned the issue to the content author to evaluate and update the document as appropriate.

[mimckitt]

@jonbeck7 any update on this?

[jonbeck7]

Yes we agree with you, we have been discussing releasing a "Naming convention" page that explains not only our historic naming but our new naming strategy. A quick sneak peak to the answer to your question:
i = isolated node
l = low memory
m = memory intensive
t = tiny memory
r = RDMA
s = Premium Storage capable (some newer sizes are also premium storage capable but missing the 's' like M128, M128m, M64, ...)

[rlisnoff]

@jonbeck7 That's a great idea, but I have a big concern with what seems to be an implied change to the conventions in your reply. My company consumes these sizes (and tags) to gain some insight into how we can better resize our VMs, and if they are changing we'd really appreciate advanced notice of how they're expected to change.

Either way, thank you for the preview and the upcoming page!

[glzbcrt]

Yes we agree with you, we have been discussing releasing a "Naming convention" page that explains not only our historic naming but our new naming strategy. A quick sneak peak to the answer to your question:
i = isolated node
l = low memory
m = memory intensive
t = tiny memory
r = RDMA
s = Premium Storage capable (some newer sizes are also premium storage capable but missing the 's' like M128, M128m, M64, ...)

Hello,

Is there any page on Microsoft Docs where we can find this information?