11–20 of 146 posts
Can those instances be used in GKE node pools?
Disclosure: I work on Google Cloud. Should be, once the rollouts complete. So once you can see N2D types in the Console for your project, I think it'll just flow naturally to GKE.
That's correct! Once the rollout completes, you will be able to use N2D instances for GKE!
Earlier quoted context omitted.
Does the new n2d machine type support nested virtualization? (Asking because Azure supports nested virtualization but only on some machine types. AWS doesn't support nested virtualization at all. Google Cloud seems to support nested virtualization on other machine types.) Also, why 224 rather than 256?
We do not yet support AMD's nested implementation (we do on Intel). But cvallejo is also the PM for Nested :). As for 224, we've always reserved threads on each host for I/O and so on. Figure 2 from the Snap paper [1] is probably the best public reference. We also don't make it clear (on purpose) what size the underlying host processors are, though you can clearly guesstimate pretty easily. [1] https://research.googl…
Any particular reason for that limitation, or just "not implemented yet"? (Not asking for product roadmaps, just wondering if there's a specific technical issue that makes it more difficult to support.)
> As for 224, we've always reserved threads on each host for I/O and so on. Figure 2 from the Snap paper [1] is probably the best public reference.
That's helpful, thank you.
Well, they may be hypothetically "available" in us-central1, but they don't show up for me. All I see is "Cascade Lake powered" N2.
Disclosure: I work on Google Cloud. cvallejo is the PM, so ask her anything!
Does the new n2d machine type support nested virtualization? (Asking because Azure supports nested virtualization but only on some machine types. AWS doesn't support nested virtualization at all. Google Cloud seems to support nested virtualization on other machine types.) Also, why 224 rather than 256?
Well, they may be hypothetically "available" in us-central1, but they don't show up for me. All I see is "Cascade Lake powered" N2.
Well, they may be hypothetically "available" in us-central1, but they don't show up for me. All I see is "Cascade Lake powered" N2.
Sorry for the confusion. We should be more clear and explicitly state "now rolling out". Over the course of our multi-day rollout, different regions and the console will start showing these.
Earlier quoted context omitted.
Disclosure: I work on Google Cloud. Should be, once the rollouts complete. So once you can see N2D types in the Console for your project, I think it'll just flow naturally to GKE.
Disclosure: I also work on Google Cloud That's correct! Once the rollout completes, you will be able to use N2D instances for GKE!
Modifying instance group templates is your friend.
Now its getting really interesting: In the end you have to compare pricing for a vCore (which is a thread on a cpu) with per-thread performance on AMD vs. Intel. Does anyone know a benchmark like this? Epyc Processors are most often tested on heavy parallelizable tasks and not strictly single thread tasks.
At this point Intel literally only makes sense if you have one of those single threaded work loads where it still excels and you absolutely must have the fastest single thread performance.
Earlier quoted context omitted.
Disclosure: I work on Google Cloud. Should be, once the rollouts complete. So once you can see N2D types in the Console for your project, I think it'll just flow naturally to GKE.
Disclosure: I also work on Google Cloud That's correct! Once the rollout completes, you will be able to use N2D instances for GKE!
Wow, half of the comments so far start with this disclosure! Tons of Google people lurking on HN :)