Skip to main content
Solved

VMware virtual Proxy CPU limit?


coolsport00
Forum|alt.badge.img+20

Hey there Community -

I know in VMCA exam’s past, there was a limit to the amount of vCPUs you could use for VMware VM Proxies due to a “stop” concern (forgot the exact issue). Is this still a problem, and if so...do you know where the documentation is which discusses this? I can’t seem to find anything in the Guides or BP Guide. I think I do have it somewhere in a previous VMCA class “handbook”. I’ll post back the statement(s) when I find it.

Thanks.

Best answer by MicoolPaul

Hey @coolsport00 its the same consideration as before, more vCPU increases the risk of co-stop, but that will depend upon your hardware & concurrent workloads.

 

The background has evolved more as vSphere has done more on NUMA awareness and Veeam enhanced NUMA awareness in VBR v11.

 

You can go above 8 vCPU certainly, you’ve just got to know where you monitor for issues

View original
Did this topic help you find an answer to your question?

4 comments

Chris.Childerhose
Forum|alt.badge.img+21
  • Veeam Legend, Veeam Vanguard
  • 8485 comments
  • October 6, 2024

I don't think a concern any more but I still follow the BP guide of 8x16 for them and scale out when more are needed.  This usually does the trick but we have done some lately with 16x32 and they work fine.


MicoolPaul
Forum|alt.badge.img+23
  • 2361 comments
  • Answer
  • October 6, 2024

Hey @coolsport00 its the same consideration as before, more vCPU increases the risk of co-stop, but that will depend upon your hardware & concurrent workloads.

 

The background has evolved more as vSphere has done more on NUMA awareness and Veeam enhanced NUMA awareness in VBR v11.

 

You can go above 8 vCPU certainly, you’ve just got to know where you monitor for issues


coolsport00
Forum|alt.badge.img+20
  • Author
  • Veeam Legend
  • 4133 comments
  • October 6, 2024

Thanks for the info guys! 


coolsport00
Forum|alt.badge.img+20
  • Author
  • Veeam Legend
  • 4133 comments
  • October 8, 2024

Ooops...forgot to share the screenshot of where I saw the co-stop info from. It was in the V1 ADO Course Handbook:

VM Proxy Co-Stop

 


Comment