Múltiple vms can still share that one core. Unless you’re crunching numbers in a vm, the core usage is likely not reaching 100%, and it can still be shared between vms. It does not exactly translate to 1 to 1
Homelab
Rules
- Be Civil.
- Post about your homelab, discussion of your homelab, questions you may have, or general discussion about transition your skill from the homelab to the workplace.
- No memes or potato images.
- We love detailed homelab builds, especially network diagrams!
- Report any posts that you feel should be brought to our attention.
- Please no shitposting or blogspam.
- No Referral Linking.
- Keep piracy discussion off of this community
You don't "assign" cores to VMs. When you create a VM and give it vCPUs, you are telling the host how many threads it can use at a given time. The hypervisor (in this case proxmox) has its own task scheduler. As work comes in from the VMs, it assigns them to available threads on the physical processor.
For example, if you have a quad core CPU, you can create as many VMs as you have RAM and other resources for and give them ALL 4 vCPUs. So you can have a single 4c/4t CPU and 10 VMs with 4 vCPUs each. Proxmox will simply balance the load using its own task scheduler and assign work to the physical CPU based on load, available threads, etc.
If you want to assess whether or not your physical processor is overloaded, you need to look at the summary for the host and see if the CPU usage and Server load stats to see if you are overusing the CPU.
You could set up monitoring of the VMs & host and determine if you have, or are approaching, a performance bottleneck. Also, if you do want increase capacity, it would be better adding a second node, so you have some redundancy in your lab.
Awesome thank you everyone! So I'll stick with what I have for now as it is more power efficient. I'm still going to toss the extra ram in when I see a good price I think.