<p><a href="https://learn.microsoft.com/en-us/azure/virtual-machines/sizes-b-series-burstable" rel="nofollow noreferrer">From Microsoft documentation, quoting</a>:</p>
<blockquote>
<p>The B-series provides you with the ability to purchase a VM size with baseline performance that can build up credits when it is using less than its baseline. When the VM has accumulated credits, the VM can burst above the baseline using up to 100% of the vCPU when your application requires higher CPU performance</p>
</blockquote>
<p>Standard_B4ms has base performance of 90% and max of 400%. Also there are variable of processors that may be used.</p>
<p>Truth could be in credits.
Credits should be checked in new and old VM in order to verify if it can burst or not.</p>

CC BY-SA 4.0
2023-03-06T02:12:47.267Z
Thanks for your answer. You may be onto something here! I compared the "CPU Credit Remaining" for each VM over the past month. It turns out that I ran my benchmark test while the new VM's "CPU Credit Remaining" was still ramping up. This could explain the difference in performance between both environments.
Sheldon
CC BY-SA 4.0
2023-03-03T12:23:08.760Z
2023-03-03T12:23:08.760Z
igiannak
<p>Our team copied a VM from one Azure subscription onto a new Azure subscription.
This VM acts as a Clickhouse client. Both the original and the copied VMs share the same characteristics: <strong>Standard B4ms (4 vcpus, 16 GiB memory)</strong>.</p>
<p>The newly created VM behaves properly, however I noted that it does not perform as well as the original VM. For instance, when trying to run a simple Clickhouse query, this is what both VMs return:</p>
<pre><code>Original VM: Processed 2.45 million rows, 9.79 MB (125.86 million rows/s., 503.44 MB/s.)
New VM:  Processed 2.45 million rows, 9.79 MB (62.26 million rows/s., 249.03 MB/s.)
</code></pre>
<p>Do you have any idea what may cause this difference in performance?</p>

<azure><performance><vm>
Performance of newly created Azure VM
Sheldon
# Performance of newly created Azure VM

(Asked by: username_0 on 2023-02-24)

Our team copied a VM from one Azure subscription onto a new Azure subscription.
This VM acts as a Clickhouse client. Both the original and the copied VMs share the same characteristics: Standard B4ms (4 vcpus, 16 GiB memory).
The newly created VM behaves properly, however I noted that it does not perform as well as the original VM. For instance, when trying to run a simple Clickhouse query, this is what both VMs return:
Original VM: Processed 2.45 million rows, 9.79 MB (125.86 million rows/s., 503.44 MB/s.)
New VM:  Processed 2.45 million rows, 9.79 MB (62.26 million rows/s., 249.03 MB/s.)

Do you have any idea what may cause this difference in performance?

**Tags:** azure, performance, vm


---

## 1 answers

### Answer by username_1 on 2023-03-03. Score: 1 | Accepted answer

[From Microsoft documentation, quoting](https://learn.microsoft.com/en-us/azure/virtual-machines/sizes-b-series-burstable):

> The B-series provides you with the ability to purchase a VM size with baseline performance that can build up credits when it is using less than its baseline. When the VM has accumulated credits, the VM can burst above the baseline using up to 100% of the vCPU when your application requires higher CPU performance

Standard\_B4ms has base performance of 90% and max of 400%. Also there are variable of processors that may be used.

Truth could be in credits.
Credits should be checked in new and old VM in order to verify if it can burst or not.

> **Comments:**
> **username_0**: Thanks for your answer. You may be onto something here! I compared the "CPU Credit Remaining" for each VM over the past month. It turns out that I ran my benchmark test while the new VM's "CPU Credit Remaining" was still ramping up. This could explain the difference in performance between both environments.  

---

