3 ms·
vCPU is a "Virtual Core", it's even in the name. When you rent those, you don't get access to a dedicated core/CPU, but one part of a logical processor. The sid
by capableweb 4y ago
vCPU is a "Virtual Core", it's even in the name. When you rent those, you don't get access to a dedicated core/CPU, but one part of a logical processor. The side channel attacks you mention all have mitigations at this point.
- yourad_io 4y agoA vCPU also represents a CPU _thread_ which is usually half a core. Sometimes you will share the CPU.
- yababa_y 4y agoOnly the very smallest instances don’t get a full core. And when you have multiple vCPU the scheduler _won’t_ ever split you onto a thread. This is definitely true of aws’s nitro, I don’t know for certain about gcp. The attacks are not fully mitigated between hyperthreads. Is there evidence cloud compute is more than a few percent slower than on-prem?
- Sohcahtoa82 4y ago> Only the very smallest instances don’t get a full core. Not sure this is true for AWS anymore. Even a t3.nano gives you 2 vCPUs, which I've always interpreted as meaning they give you 1 core with two threads to ensure that you never share a core with another tenant. Of course, t2 instances still exist which give 1 vCPU, but there's no reason to create one of those when a t3 gives 2 vCPUs at a lower price. The only reason to be running a t2 is if you created it before t3 existed and just haven't bothered migrating.