[dragontamer]

I don't know. I prefer it when companies actually give the technical details.

> While we are still optimizing these instances, it is clear that the Graviton3 is going to deliver amazing performance. In comparison to the Graviton2, the Graviton3 will deliver up to 25% more compute performance and up to twice as much floating point & cryptographic performance. On the machine learning side, Graviton3 includes support for bfloat16 data and will be able to deliver up to 3x better performance.

This means nothing to me. Why is there more floating point and cryptographic performance? Did Amazon change the Neoverse core? Is this N1 cores still? Did they tweak the L1 caches?

I don't think Amazon has the ability to change the core design unfortunately. This suggests to me that maybe Amazon is using N2 cores now?

But it'd be better if Amazon actually said what the core design changes are. Even just saying "updated to Neoverse N2" would go a long way to our collective understanding.

[talawahtech]

AWS re:Invent is this week. This was announced as part of the CEO's keynote. I am sure we will get more details throughout the week in some of the more technical sessions.

[ksec]

>Why is there more floating point and cryptographic performance?

You can infer this to N2 which ARM gave their own results [1], N2 uses SVE2 256bit.

[1] https://community.arm.com/arm-community-blogs/b/architecture...

[SecurityPony]

N2 does not use 256b SVE2, though its cousin Neoverse V1 does. I think there's a very real chance that Grav3 is actually V1, not N2. (N2 uses 128b SVE vectors, as does the Cortex-A710 it's based on.)

[ksec]

Oh YES [1] . I got the two mixed up. I should have doubled checked. So it is V1.

The V1 design is available in both 7nm and 5nm.

Oh well I guess if AWS had it in 5nm they would have at least marketed it as such. So may be it is the same 7nm.

[1] https://images.anandtech.com/doci/16640/Neoverse_Intro_3.png