3 ms·
It's unlikely a different die (silicon chip), so the usual number of cores and usual size of caches, and it's unlikely that AWS gets a secret x86 instruction un
by wolf550e 5y ago
It's unlikely a different die (silicon chip), so the usual number of cores and usual size of caches, and it's unlikely that AWS gets a secret x86 instruction unlockable via msr or something like that. It's probably just constants for the frequency scaling (e.g. all cores and single core turbo).
Cloudflare mentioned they use a custom Intel SKU on their blog, and they're not as big as AWS.
- ghbe44 5y agoI’m familiar with Google’s custom SKUs, and I assure you they’re unique enough to experience microcode bugs nobody else on the planet ever hits. There was a weird FDIV one back in the day that wasn’t the same FDIV bug that hit us all a long time ago. Cloudflare isn’t really at that customization table. Your take sounds accurate for non-FAANGs (and a couple of those). For Google, not so much. There is a lot of custom acceleration and such that isn’t available to any other customer, and a nearby commenter is right, every detail about them is locked behind a very strong NDA. I’ve heard thirdhand AWS does indeed have custom instructions in the virtualization extensions stuff, but don’t know if that’s true.
- monocasa 5y agoMy understanding is that Google's SKUs are the same die. Non Google versions just have the Google specific silicon fused off, or require a MSR knock sequence to turn on.