- Jul 27, 2020
- 26,020
- 17,952
- 146
Nuh uh. Don't take the easy way out. Don't be lazy. DISSECT my post and tell me why it gives you the impression that I'm NOT okayAre... are you okay?
Nuh uh. Don't take the easy way out. Don't be lazy. DISSECT my post and tell me why it gives you the impression that I'm NOT okayAre... are you okay?
Hey, what's stopping Intel from gluing together two rejected 8+0 Alder/Raptor Lake dies, each with only 6 cores active?That's still very much a rumor. I see no benefit in Intel making a new die of a soon to be outdated, problematic core. We also don't know what clocks might be before they run into a power limit. I expect ARL and Zen 5 to perform better injust aboutevery scenario.
That's still very much a rumor. I see no benefit in Intel making a new die of a soon to be outdated, problematic core. We also don't know what clocks might be before they run into a power limit. I expect ARL and Zen 5 to perform better injust aboutevery scenario. Consoles are limited to 8 Zen 2 cores so I don't know what you think you are missing out on.
Hey, what's stopping Intel from gluing together two rejected 8+0 Alder/Raptor Lake dies, each with only 6 cores active?
They have done it before with with P4 and (possibly because not sure what their last glue-y CPU was) most recently this: https://overclock3d.net/news/cpu_ma...th-up-to-48-cores-with-glued-together-design/
Hey, maybe they have a huge stock of eDRAM lying around that they could pair with that glue-y CPU die.Though if Intel does what you say it would not be a 12 + 0 die. It would instead be 2 6 + 0 dies of Golden Cove glued together. Intel does have a 6 + 0 die of Alder Lake the 12400 and 12500 and 12600 non K.
Nuh uh. Don't take the easy way out. Don't be lazy. DISSECT my post and tell me why it gives you the impression that I'm NOT okay![]()
Sorry but you are making yourself sound like an Intel spokesperson. What about Zen4c/5c having AVX-512? How does it make sense for them having it?Intel not doing AVX512 on Atom has little to do with being "wimpy" and everything to do with the fact that their Atom value proposition banks on significant general-purpose area-efficiency advantages over Core (with 4 Gracemont being the same area as one Golden Cove and delivering double the throughput performance, according to Intel in the ADL days.) AVX512 units are chunky and don't contribute to normal-application general-purpose performance. Therefore, they are left out. Could Intel make the penalty smaller by supporting AVX512 on 256b units? Sure, but it still wouldn't be free or close to it - it assumes a whole extra state, extra ISA features for stuff like masks, etc. That stuff isn't free on area and it isn't free on the cost of validation.
Intel has done AVX512 on Atom before, with KNL, because that was a product where it made sense (and one they severely mismanaged.)
Sorry but you are making yourself sound like an Intel spokesperson.
What about Zen4c/5c having AVX-512? How does it make sense for them having it?
Just admit it. Intel is too lazy and too greedy to promote their own technology to consumers and leave it to the maverick competitor to do so.
Gracemont isn't even a child of anything remotely resembling an Atom core. It's a frickin' Skylake analogue. If you want to call something the descendant of Atom, let it be the LP E-cores in Meteor Lake. No Atom AFAIK consumed as much power as Gracemont.
These comments? https://forums.anandtech.com/thread...m-cpu-market-stagnation.2616907/post-41135729
Please elaborate how the last gen Intel CPUs are not covered by your comments.
yeah ..Their 9950X ES is already eating 300W@Unlimited power. That should be more than enough for 40 threads and possibly even for 48 threads since the Zen5c CCD isn't going to eat power like the fat CCD.
If Pat weren't such a feeble old CEO, we would've seen a 40 core K or KS CPU from Intel by now because a CEO with enough testosterone would ABSOLUTELY DEMAND it!
That story is meaningless to me unless you tell me which CPU it was that arrived three years late (Lakefield?) and the codename of the cousin (Lakefield had a cousin??? Darn it!).Let me tell you an Intel story. They were laboring upon a multicore processor with some new I/O tech. The core itself was nothing remarkable - a simple rev of what had come before. It was, however, supposed to be a product of three different design centers that hadn't worked together before.
They didn't play nicely with each other - different siloes, different people, different ways of doing things - and it ended up three years late, by which time it was completely uncompetitive. This processor's cousin, which used the same I/O tech, ended up being entirely canceled because the new design group that was created to work on it was poorly managed. A bunch of people got laid off.
OUCH! Well, I suck at learning and you wouldn't have the patience to teach me, let alone the charitable inclinationGracemont is a clear and direct derivative of Tremont, which itself has a clear lineage from Goldmont. You would know this if you spent more time learning about microarchitecture and less time ranting on forums.
That story is meaningless to me unless you tell me which CPU it was that arrived three years late (Lakefield?) and the codename of the cousin (Lakefield had a cousin??? Darn it!).
OUCH! Well, I suck at learning and you wouldn't have the patience to teach me, let alone the charitable inclination
BUT, I think you mean this Tremont being compared to a similar Gracemont alternative: https://ark.intel.com/content/www/us/en/ark/compare.html?productIds=212329,231803 ?
Both are based on similar process (ok maybe the GMont process is slightly more refined) but the GMont has turbo boost enabled and has more cache yet it has the same TDP??? Intel is clearly LYING here because: https://chipsandcheese.com/2021/12/21/gracemont-revenge-of-the-atom-cores/
View attachment 103864
GMont may be a direct derivative of Tremont but it is too muscular and power hungry to be considered an Atom. Saying GMont is Atom is like saying C++ is like C when the former is a massively bloated mess.
Sarah, Sarah, Sarah. I think I can agree with you on many things but GMont being Atom ain't one of them.
I mean, Atom is a name for a uarch family. It isn't a generic term for "core power under 3W" or whatever. Every descendant of Silvermont has been a clear evolution of its predecessor.
List of Intel Atom processors - Wikipedia
en.wikipedia.org
No Gracemont CPU in that list.
![]()
Gracemont (microarchitecture) - Wikipedia
en.wikipedia.org
The Atom branded Gracemont there with 6W TDP is dual core while the quad core has 12W TDP.
Power consumption of Gracemont has clearly ballooned to the point that it does not resemble its immediate predecessor. But I guess you "win" because Intel is still calling it Atom. Basterds.
8c 1.8GHz Gracemont in 15W TDP is entirely in line with past Atoms. Better than a lot of them, even. Its perf/W is drastically better than that of Tremont.
Overall, this is more power than the older N5105 units, but we are also getting a lot more performance.
![]()
Almost a Decade in the Making Our Fanless Intel i3-N305 2.5GbE Firewall Review
We review the biggest advancement in a decade in this fanless Intel Core i3-N305 fanless firewall review and see new storage features as wellwww.servethehome.com
Intel didn't miraculously increase performance at same power levels. Everywhere I look, it says more power consumption.
Yes, dear. Whatever you say, dear.I'ma stand by "perf/W drastically better than that of Tremont", thanks.
what? AVX512 isn’t present because it would make the ecores ISA incompatible with the pcores. It’s not a conspiracy theory, I don’t think Intel cares if you disable the ecores on a product you’ve already purchased from them.Intel pulled it from their CPUs to stop almost every gamer from turning off E-cores (which they still do, ironically).
avx-512 is not even avail for the lasdt 2 generations, why are we still talking about this ???what? AVX512 isn’t present because it would make the ecores ISA incompatible with the pcores. It’s not a conspiracy theory, I don’t think Intel cares if you disable the ecores on a product you’ve already purchased from them.
How do you explain Alder Lake launch SKUs coming out with AVX-512 available when E-cores were disabled in BIOS from all the Taiwanese mobo manufacturers?I don’t think Intel cares if you disable the ecores on a product you’ve already purchased from them.
Apparently some people are still confused why exactly Intel disabled AVX-512.avx-512 is not even avail for the lasdt 2 generations, why are we still talking about this ???
Wait, I thought the conspiracy was that Intel didn't want you to disable ecores? Which is it?Apparently some people are still confused why exactly Intel disabled AVX-512.
I guess there were WIDESPREAD reports of applications bluescreening Windows when AVX-512 threads got migrated onto E-cores yet the media failed to report that. /s
A secret: Intel was deathly scared that someone would figure out through hacking how to run BOTH E-cores and P-cores with AVX-512 enabled and then devise some sort of software trickery to keep AVX-512 threads from being bounced over to E-cores thus maintaining perfect compatibility for all applications. Intel did NOT want that because then the solution wouldn't come from inside Intel. It would make Intel look really bad. Intel had to do something to destroy any chance of such a PR nightmare happening. So they rolled out an urgent and mandatory irreversible microcode update to disable AVX-512 on all existing and future Alder/Raptor Lake CPUs. Intel now sleeps in peace, only awakened from time to time by the horrific voices of users cursing them when their Unreal Engine 5 based games crash. It's less of an issue than being made to look like fools who couldn't figure out on their own how to make AVX-512 and E-cores co-exist.
On a superficial level, they don't want the E-cores to be disabled coz it throws a shade on their hard work and makes the CPU weaker in MT workloads.Wait, I thought the conspiracy was that Intel didn't want you to disable ecores? Which is it?
I think the simplest explanation works best in this case. They disabled the option so they would have less stuff to validate and debug in case of problems, right now they don't need to check if AVX works on the off-chance that somebody might want to use it, when majority don't even know what it is. This wouldn't show up in gaming benchmarks, would not affect Cinebench etc. Like right now AMD is winning in decompression benchmarks for years, and does anyone care, mocks intel for that etc.On a superficial level, they don't want the E-cores to be disabled coz it throws a shade on their hard work and makes the CPU weaker in MT workloads.
At a deeper level, what I said in the previous post about them (certain engineering heads) not wanting an AVX-512+E-core co-existence solution getting worked out by the community through some hack.
I just thought of a new serious drawback for Intel in exposing AVX-512: their 16 AVX-512 threads getting pounded in benchmarks by 32 7950X threads. So they disabled the ability to make such comparisons rather than be mocked publicly by review sites.
But games do not care much about more cores.Does not matter. Gimped cache is gimped performance and games love cache.