3 ms·

AWS behind Azure, GCP, and even Oracle Cloud in this release. Azure had EPYC Rome available 6 months ago. Surprising, AWS had been among the fastest to roll out

by gundmc 6y ago

AWS behind Azure, GCP, and even Oracle Cloud in this release. Azure had EPYC Rome available 6 months ago. Surprising, AWS had been among the fastest to roll out new hardware in the past few years.

markgavalda 6y ago
Mostly Intel hardware though if I'm not mistaken?
- gundmc 6y ago
  Yeah, we'll have to see how quickly the various providers are able to get EPYC Milan GA'ed once it's available.
  - _msw_ 6y ago
    Disclosure: I work for AWS building cloud infrastructure My experience working at Amazon has changed my thinking about how to deliver great customer experiences. When we make a new EC2 instance available, customers expect to be able to use it at scale that is indistinguishable from limitless (which is a challenge in a world that has physical constraints in accordance to laws of physics), instantaneous availability, and high quality. This requires significant infrastructure deployment scale and careful design and management of supply chains. Not every provider has the same philosophy and approach in practices.
rajnathani 6y ago
There's a catch though. We primarily use GCP - About a month and a half ago we were planning to run a large compute job, since GCP already had these great performance-to-cost AMD EPYC 2nd gen Rome VMs available then, we decided to use them, only to find out later that there was a service quota of 24 vCPUs for these instances. The worse part of it was that it wasn't even clear in the service quota page that there was no point in requesting anything beyond 24, as for whatever number we put 512, 256, 128, 32, etc. for all cases we would get automatically rejected. Essentially it was a hard quota limit, and in principle it felt like it went against the launch blog post [0] of GCP stating a case of 224 vCPUs of these new EPYC processors being used at a time. I'm not sure what the service quota is like on AWS, however it could be that AWS waited to procure enough of these new EPYC processors to be able to provide a reasonable amount of such compute for their large customer base. [0] https://cloud.google.com/blog/products/compute/announcing-the-n2d-vm-family-based-on-amd https://cloud.google.com/blog/products/compute/announcing-th...

by gundmc 6y ago

AWS behind Azure, GCP, and even Oracle Cloud in this release. Azure had EPYC Rome available 6 months ago. Surprising, AWS had been among the fastest to roll out new hardware in the past few years.

markgavalda 6y ago

Mostly Intel hardware though if I'm not mistaken?

gundmc 6y ago
Yeah, we'll have to see how quickly the various providers are able to get EPYC Milan GA'ed once it's available.
- _msw_ 6y ago
  Disclosure: I work for AWS building cloud infrastructure My experience working at Amazon has changed my thinking about how to deliver great customer experiences. When we make a new EC2 instance available, customers expect to be able to use it at scale that is indistinguishable from limitless (which is a challenge in a world that has physical constraints in accordance to laws of physics), instantaneous availability, and high quality. This requires significant infrastructure deployment scale and careful design and management of supply chains. Not every provider has the same philosophy and approach in practices.

rajnathani 6y ago

There's a catch though. We primarily use GCP - About a month and a half ago we were planning to run a large compute job, since GCP already had these great performance-to-cost AMD EPYC 2nd gen Rome VMs available then, we decided to use them, only to find out later that there was a service quota of 24 vCPUs for these instances. The worse part of it was that it wasn't even clear in the service quota page that there was no point in requesting anything beyond 24, as for whatever number we put 512, 256, 128, 32, etc. for all cases we would get automatically rejected. Essentially it was a hard quota limit, and in principle it felt like it went against the launch blog post [0] of GCP stating a case of 224 vCPUs of these new EPYC processors being used at a time. I'm not sure what the service quota is like on AWS, however it could be that AWS waited to procure enough of these new EPYC processors to be able to provide a reasonable amount of such compute for their large customer base. [0] https://cloud.google.com/blog/products/compute/announcing-the-n2d-vm-family-based-on-amd https://cloud.google.com/blog/products/compute/announcing-th...