Put simply, Azure B Series virtual machines will only operate at about 1/3rd of their CPU potential most of the time.
Microsoft recommends B-Series for “burst” workloads, and not continuous loads and they make that work using a credit system to stop these VM’s from hogging the CPU.
For instance a common B-Series Azure Machine Size is “Standard_B8ms” which under normal conditions, the CPU max’s at 33% (i.e. ROUGH equivalent of 2.7 cores in an 8 core VM) but can burst to 100% until its credits run out causing it to slow back to 33% for at least 1 hour.
Notably, credits reset to zero after every reboot, start adding to the credit bank immediately on power up, and max out after 24 hours (see table below for details).
This makes B-Series VM’s good for services that get busy periodically but often slow back down. In most companies, this would include Domain Controller VM’s, Print Servers, File Servers and low use FTP servers.
Lets look at one example using two different B Series Burstable Virtual Machine Sizes.
You could use an Azure D-Series Gen 5 Size for $570/month and get 8 cores with 32GB of memory that you can run full tilt all day and all night. This is the least cost option if the the server’s cores are busy all the time.
This is a difficult question to answer because Microsoft using servers with CPU’s that were released in 2014 all the way through to CPU’s released in 2020. As of January 2024 here is the list of CPU’s you could get assigned to you if you use Azure B Series:
The Azure B Series Size VM’s do NOT support Nested Virtual Machines, only have a few versions that allow Accelerated Networking, and the bottom level “B1” is only supported on Linux deployments.
This website uses cookies.