Here, for example, Amazon's own Aurora MySQL is not available on Graviton processors.
Here, for example, Amazon's own Aurora MySQL is not available on Graviton processors.
It is not surprising at all that supported products are going to be slow to support other architecture.
Basically, although I'm sure someone will shout me down for this, x86 provides something close to sequential consistency among loads and stores even for concurrent programs, whereas ARM and POWER provide almost no kind of order for loads and stores without barriers. High-level languages like C++ do not really hide this problem. It is very easy to write a concurrent C++ program on x86 that appears to work in practice but never works on ARM.
On x86, sequential consistency isn't the implemented memory model, but rather total store ordering. Stores are buffered inside the core and the guarantee provided is that they'll appear to other cores in the proper order. On SC designs, all the cores have the same view of coherent memory all the time. In such a design, barriers aren't required and are lowered down to NOPs.
(only general-purpose processors that I know of that implement sequential consistency are NVIDIA's Tegra K1 (64-bit variant) and Tegra Xavier)
I had to take a peek at a friend's Cavium's ThunderX2 kernel issue a while back, which stops having concurrency when release build is swapped with a debug build.
So the specific part that drives you crazy is "Atomic can be reordered with stores - Y" for ARM and N for X86_64.
And changing the compiler optimization flags can turn on/off this bug.
It's like Amazon has narrowly tested specific features on specific hardware sizes.
Amazon Aurora support for AWS Graviton2 powered instances is still in development. I'll share your comments with the team, since direct customer feedback helps us prioritize new launches. If you have an account manager, please also let them know to make a note on your specific interest.
Do specific customer requests change the development trajectory significantly?
For Amazon Aurora, there are a lot of additional features in development, including offering Graviton2-powered instances. I expect that will deliver price and performance benefits for customers, but it's not the only benefit that's in the works.
For the container systems e.g. ECS, EKS, Fargate they have an open roadmap where they drive much of the direction from the community:
https://github.com/aws/containers-roadmap
For others it's completely closed off. At my last company we spent tens of millions a year with AWS and they never listened to us. The account managers have zero pull.