Digital Foundry : Google Stadia Specs Analysis + Exclusive Performance Testing

[Bofferbrauer2]

Pemalite said:

The latency is probably not going to be an issue for everyone. - And yet, latency is going to be a catastrophic issue for some, physically the closest Google server for me is half a continent away.

The compression artifacts that reduce visuals is also not going to be an issue for everyone, if everyone cared about visuals, everyone would be a PC Gamer and the Wii wouldn't have been the success it was.

I think it will be interesting to see where Google takes this... With Vega 56 levels of GPU grunt backing it, it might just surprise... But one thing is for sure, if anyone is able to take the fight to Sony, Nintendo, Microsoft and potentially be successful... It's Google.

And no two ways about it, this is likely the future of gaming, just not for me though. I like my games rendered locally.

Yeah, it's a 56CU GPU, but too fast for it. I'm wondering if they are using MI50 with 4 deactivated CU instead, as that would fit performance wise.

But what intrigues me more is the CPU. 9.5MB of combined L2+L3 cache is both a very weird number and an awfully low amount of CPU cache nowadays. Also, I couldn't find a chip with those specs, no Core, no Xeon, no Ryzen or Epyc fits the description. My guess is it's based on a Coffee Lake Xeon E 2176M, but with less L3 cache (8 instead of 12MB, with the missing 1.5MB coming from the 256KiB per core) and probably lower boost clocks (only the all-core boost really matters in servers anyway).