News for hackers. Stuff that matters.

A comment on Hertzbleed Attack. Parent comment

Re:Hertzbleed Attack by staindk on Tuesday June 14, 2022 @02:26PM (#31743757)
I think this means you were paying for the over-provisioning i.e. paying for a full CPU or baremetal server?

"The Cloud" is all about vCPU - "2 vCPUs" feels somewhat standard for a base-tier VPS... and 2 vCPUs means "2 virtual CPUs" or rather "roughly equivalent to 2 CPU cores" I think. I understand that jargon to mean they are always cramming 11 x 2vCPU clients onto 20 physical cores.

[ Parent | on HN ]
Re:Hertzbleed Attack by phamilton on Tuesday June 14, 2022 @02:31PM (#31743828)
Nah, vCPU is generally just hyperthreading. See https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/cpu-opti...

So you get 2 vCPUs per core.

[ Parent | on HN ]
Re:Hertzbleed Attack by staindk on Tuesday June 14, 2022 @02:44PM (#31744033)
Thanks for the link, that's great to know about AWS.

I don't think all other VPS providers are that good about things - googling around for some other definitions of vCPU (in VPS context) I see a lot of examples of 16 thread server CPUs handling "128 vCPUs".

[ Parent | on HN ]
Re:Hertzbleed Attack by ceeplusplus on Tuesday June 14, 2022 @02:32PM (#31743840)
No, 2 vCPUs is 2 logical threads, which is equivalent to a single physical core on x86. So yeah, they are cramming 11 x 2 vCPUs onto 20 physical cores. In fact, it's more like 20 x 2 vCPUs.
[ Parent | on HN ]
Re:Hertzbleed Attack by sofixa on Tuesday June 14, 2022 @02:31PM (#31743825)
Depends on the cloud - OVH and Digital Ocean yes, but AWS give you whole uncontested cores ( bar the t* instance line, but that's it's whole thing).
[ Parent | on HN ]