3 ms·
Intel is not really screwed, cloud providers are. Those "vCPUs" people have been buying are actually hyperthreads. I have a hypothesis that a double digit perce
by m0zg 7y ago
Intel is not really screwed, cloud providers are. Those "vCPUs" people have been buying are actually hyperthreads. I have a hypothesis that a double digit percentage of cloud customers don't know what vCPUs are. As a cloud provide, imagine cutting your fake "core capacity" in half _and_ having to raise prices to offset the increased capex.
- AaronFriel 7y agoI've had difficulty parsing the guidance from Google for Google Kubernetes Engine here: https://cloud.google.com/kubernetes-engine/docs/security-bulletins#may-14-2019 https://cloud.google.com/kubernetes-engine/docs/security-bul... > Note that n1-standard-1 (the GKE default), g1-small and f1-micro VMs only expose 1 vCPU to the guest environment so there is no need to disable Hyper-Threading. I'm wondering if they've decided to just eat the loss on the single vCPU nodes, and for vCPUs >= 2, they pass the decision on to the customer. Or is there someone else's VM running on the other hyperthread? Here's their guidance on machine types: https://cloud.google.com/compute/docs/machine-types https://cloud.google.com/compute/docs/machine-types > For the n1 series of machine types, a vCPU is implemented as a single hardware hyper-thread on one of the available CPU Platforms.
- deleted 7y ago[deleted]
- WrtCdEvrydy 7y agoThis is why the last version of AWS ARM had their vCPUs being 30% faster than regular vCPUs (no HT in ARM)