Anon (no.delete@this.thanks.com) on December 3, 2021 6:52 am wrote:
> Kara (karaardalan.delete@this.gmail.com) on December 3, 2021 6:36 am wrote:
> > none (none.delete@this.none.com) on December 3, 2021 6:19 am wrote:
> > > Kara (karaardalan.delete@this.gmail.com) on December 3, 2021 6:05 am wrote:
> > > > Adrian (a.delete@this.acm.org) on December 3, 2021 5:51 am wrote:
> > > > >
> > > > > https://www.nextplatform.com/2021/12/02/aws-goes-wide-and-deep-with-graviton3-server-chip/
> > > > >
> > > > >
> > > >
> > > > The N2 is described much wider here than Arm has ever disclosed.
> > > > I hate it when companies do this, like give some info what's gonna happen?
> > >
> > > What description of N2 is there in that article? I only see guesses.
> >
> > I meant the guesses, it's so not ARM to design 8 wide decode and 15 wide issue
> > mArchs. 64kb l1i cache wouldn't be able to keep up Nor the punly ROBs, how
> > do you feed such a wide core? Without smt or legendry l1i and rob?
> >
> > Neoverses are targeted toward server processors, making them wider doesn't make any sense.
>
> I thought that this was the V1 core? Aimed at maximum perf per thread.


Amazon did not disclose which core they have used, but what was said matches better N2 than V1.

Choosing N2 also makes more sense for Amazon, because they are more interested in general-purpose performance within a given power consumption than on performance when only few threads are active or performance for floating-point applications.