Update: AMD has officially announced the Ryzen 7 9800X3D, launching at $479.
Original story: It's no secret that leaked performance figures. These assumptions, it seems, are now officially verified, though not by AMD.
It's not AMD but motherboard manufacturers that have let this info slip—or, rather, shouted from the rooftops. Gigabyte let this slip by showing an 8-core 9800X3D on its BIOS page while advertising its new X3D Turbo Mode (which, by the way, apparently just disables SMT).
The possible slip from Gigabyte is nothing compared to MSI's rooftop announcement, though, as the company says it's "thrilled to introduce the AMD Ryzen 7 9800X3D". This is followed by four other named mentions of the 9800X3D in its three-paragraph post that reads more like an AMD U announcement than a motherboard compatibility one.
Nor is it anything compared to ASRock's similar announcement, which, to be fair to ASRock, does at least read more like a compatibility announcement than a U release announcement. The company states its "AM5 series motherboards are fully compatible with the AMD Ryzen 7 9800X3D processor, maximizing its impressive gaming performance."
And, if we needed it spelled out even clearer, ASRock continues, "The AMD Ryzen 7 9800X3D is the first model released in the 9000X3D processor series"
I'm not sure whether this is AMD giving the go-ahead, motherboard manufacturers spotting loopholes in an embargo, or just caution-to-the-wind excitement. Whatever the case—it matters not—we now have confirmation that it will be the Ryzen 7 9800X3D hitting the market next week.
This cache-heavy U could end up being one of the Ryzen 7 7800X3D. We still have no official word on specifications nor real-world gaming performance, though.
Nor do we have an official word on pricing. However, 9000X3D chips won't be cheap because "AMD is in a position where it can charge whatever it likes for its golden gaming goose".
We'll have to wait for official word from AMD on that, though. Or heck, maybe pricing info will come from MSI, ASRock, and Gigabyte. Why not, eh?
