News for hackers. Stuff that matters.
Re:GCP, AWS, and Azure ARM-based server performance comparison by daneel_w on Sunday September 25, 2022 @06:11AM (#32970130)
Not to be forgotten: per-core shared tenancy. I'd love to be proven wrong, but I doubt AWS allocates a full core for every non-burstable Arm "vCPU" sold.
Re:GCP, AWS, and Azure ARM-based server performance comparison by lathiat on Sunday September 25, 2022 @10:14AM (#32971541)
It was my understanding Amazon does in fact do this for most instance types, it's why the amount of RAM and other resources scales with CPU core count.

There are exceptions though in the very small "burstable" etc instances, like the micro etc.

EDIT: Seems I am wrong.

"Each vCPU is a thread of a CPU core, except for T2 instances and instances powered by AWS Graviton2 processors."

From: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance...

Re:GCP, AWS, and Azure ARM-based server performance comparison by electroly on Sunday September 25, 2022 @10:18PM (#32978587)
The exception for Graviton here is because every ARM vCPU is a full core, whereas an Intel/AMD vCPU is one hyperthread (i.e. half a core). They're not saying Graviton2 cores are shared. For Intel/AMD, you always get allocated both hyperthreads on a dedicated core; that's why hyperthreaded families start at 2 vCPUs. Only the "T" families feature shared cores.
Re:GCP, AWS, and Azure ARM-based server performance comparison by dijit on Sunday September 25, 2022 @06:38AM (#32970220)
Google does, this was a real sticking point for me when I was evaluating cloud options, at the time GCP was the only provider allocating (and affining) CPU cores to tennants