glg wrote:
IINM, it's not quite that perfect. I'm pretty sure I've read here that the virual core to physical core mapping is preassigned, not dynamic, so if there are two linodes pegging CPU, the odds are that they'll conflict on at least one (meaning at least one other one is sitting idle).
That said, if I'm doing the binomial coefficient right (8 choose 4), there are 70 possible combinations of cores to be assigned, so with 40 linodes per box (not sure if that's still the max or not), there needn't be any linodes with the exact same set of 4 cores, but I'm not sure how xen and/or linode does it. ie, does it just assign cores 1/2/3/4 to half and 5/6/7/8 to half or does it do a distribution so that no two have the same set of cores.
It depends on the scheduler and the admin. You can pin VCPUs to real CPUs if you want to, and that might be useful in certain specific enterprise environments where it matters, but it seems silly in a hosting environment like Linode.
The credit-based scheduler, which I believe is slated to eventually become the only scheduler supported, does automatic load balancing of VCPUs to real CPUs, if you don't pin. As for if the other schedulers support this, or which scheduler Linode uses, no clue.
It's very rare for CPU power to be an issue on a linode, though.