• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Virtual Sockets vs Virtual Cores Game Server

L

Landmine

Limp Gawd
Joined
Oct 19, 2011
Messages
402
So I have a home server and I'm making a game server VM, the server software will only use 1 thread. And that got me thinking, what is best for different setups?

What if the primary difference between virtual sockets and cores when it comes to performance?

Any recommended configurations for different build types? Database, Web Server, File Server, ect...

Thanks for the knowledge all!
 
Doesn't matter. You can do it either way in VMware. They basically added it because of software that was licensed per CPU socket so you could give a VM multiple vCPUs without each appearing as a socket.
 
If your motherboard has multiple sockets and uses NUMA, and you assign either more CPUs or more RAM than one socket has, then the VM host necessarily spreads the VM across multiple NUMA nodes, now if you don't also tell the guest VM that there are multiple NUMA sockets then it will just assume that it has a ton of cores and/or a ton of RAM all on one socket and may assign RAM on CPU1 to a thread on CPU0 or vice versa causing both CPUs to have to talk to each other to deliver said RAM to the core instead of directly accessing attached RAM, which is considerably slower.

Basically if you're making a large VM that has near, as many, or more cores or RAM that a single socket has then use NUMA on the VM. If the VM only uses one or two cores and a small fraction of RAM then don't bother with sockets. If you've got a medium sized VM (say half or more of the amount of cores or RAM in a socket) that might get croweded across sockets depending on what else is going on in the host, then keep an eye on it and enable NUMA if performance seems abnormally low for what it should be.

I guess the only exception would be a large VM that's running something with per-socket licensing that you're trying to cheese, but if you start running into the cross socket memory access issue then chances are your dual+ CPU system will run worse than a single socket one anyway.
 
You must log in or register to reply here.
Back
Top