Place CPU topology settings in plan instead of template
I feel like the CPU topology setting should be on the plan pages not in the template page. As plans dictate the amount of vCPUs on a VPS, not the template and so that makes no sense. The rest such as passthrough, make sense as these can matter per operating system such as Windows. This way everyone can properly set CPU topology globally and correctly for each plan.
Without CPU topology, operating systems don't recognize the structure as it is. They detect the allocated vCPUs as sockets, so giving a VPS 2 vCPUs means the operating system detects it as 2 sockets 2 cores for example. Just feel like it would just be a wise update to allow CPU topology to be set with a plan not a template, or both could be an option even.
9
votes
Bato
shared this idea