Hi , im having a vm whose size is F4s, and it is said that this size has the clock speed about 2.60ghz or 2.70ghz ] 2 but when i check it on my vps, it doesnt show the same this is how my vm looks like in the cônsole anyone know what's the issue here, thanks in advance

@Angellia What you are looking at in Task Manager is not an accurate representation of the maximum CPU usage that your VM can get. For Example, here is what my laptop currently shows for CPU under task manager: The VM has to be under a high CPU load in order to reach the maximum documented performance. The CPU benchmarking doc lists how the benchmarks were obtained and how they can be reproduced . Any CPU benchmarking tool should show similar results. Please let me know if you have any additional questions.

Hi Angellia, I have seen this before. It happens with windows task manger showing different values on CPU clock speed. But no yet any documented workaround available.

My Azure Vm doesnt have the same infor like the document

Angellia 21

Hi , im having a vm whose size is F4s, and it is said that this size has the clock speed about 2.60ghz or 2.70ghz ![134947-image.png ]2

but when i check it on my vps, it doesnt show the same

this is how my vm looks like in the cônsole

anyone know what's the issue here, thanks in advance

2 answers

TravisCragg-MSFT 5,686 Reputation points Microsoft Employee

2021-09-25T01:30:03.247+00:00

@Angellia What you are looking at in Task Manager is not an accurate representation of the maximum CPU usage that your VM can get. For Example, here is what my laptop currently shows for CPU under task manager:

The VM has to be under a high CPU load in order to reach the maximum documented performance. The CPU benchmarking doc lists how the benchmarks were obtained and how they can be reproduced.

Any CPU benchmarking tool should show similar results. Please let me know if you have any additional questions.
Please sign in to rate this answer.
Angellia 21 Reputation points

2021-09-25T01:34:05.35+00:00

it's ur personal computer so it's different from a virtual one. In the azure vm the clock speed number also permanent it doesnt even change at any time. it is freeze at the number as Base Speed

Angellia 21 Reputation points

2021-09-25T01:48:34.07+00:00

and you can also look at the cpu name, with my size it must be Intel(R) Xeon(R) Platinum 8168 CPU @

TravisCragg-MSFT 5,686 Reputation points Microsoft Employee

2021-09-25T01:54:53.877+00:00

Thanks for the clarification! I see what you are referring to with the listed CPU type & listed maximum throughput. I will need to deploy a few VMs and see if this behavior is similar across different VM sizes, or if this is something isolated to this particular size, or possibly an issue with your individual VM.

Angellia 21 Reputation points

2021-09-25T01:58:48.503+00:00

thanks, for more details. my vm was resized from ds3_v2 to fs4, and the current cpu, E5-2673 V4 @2.30ghz (base on this site) belongs to ds3_v2.

Although i resized to fs4, the cpu didnt change, but the cpu core and ram was still channged
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Devaraj G 2,096 Reputation points

2021-09-25T10:56:07.927+00:00

Hi Angellia, I have seen this before. It happens with windows task manger showing different values on CPU clock speed. But no yet any documented workaround available.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

My Azure Vm doesnt have the same infor like the document

2 answers

Your answer