- Mar 3, 2017
- 1,777
- 6,789
- 136
Hmm, now that you mention it, nothing about this leak says Ryzen...being AMD likes to disappoint the enthusiasts and all, I bet the dual X3D chip is merely that, an AM5 compatible EPYC SKU. Probably not going to be for consumers at all.They will probably do both, consumer and Epyc 4005 models.
Doesn't matter. It's AM5. It would be nice to launch it as an Epyc to avoid gamers thinking they should buy them.Hmm, now that you mention it...being AMD likes to disappoint the enthusiasts and all, I bet the dual X3D chip is merely that, an AM5 compatible EPYC SKU. Probably not going to be for consumers at all.
Which it should have been from start - with AAA level chiplets, both of them - $999, but plenty of gamers would buy it to feed 5090I bet the dual X3D chip is merely that, an AM5 compatible EPYC SKU.
Even more if they raise the Fmax to 6 GHz.It would be interesting if they put 2 top binned chip
https://chipsandcheese.com/p/running-gaming-workloads-through a pity he doesn't have a x3d part to compare.
For those who haven't read the article yet: As far as I have registered, it contains some good discussion of how Zen 5 and Lion Cove have similar yet different bottlenecks in game workloads, furthermore game workload traces put in contrast to SPEC traces, and also some IMO enlightening bits about games versus inter-CCX traffic. Finally somebody who, rather than merely speculating about the latter effects, did some actual performance counter based monitoring.The most important chart from there, in my opinion, and the corresponding 285K chart: [...]
That 4% advantage example is a super dubious claim for the benefits of X3D in transcoding. Thats margin of error stuff. I'd bet adding a second vcache die would not add another 4%, if anything at all. Certainly nothing worth the extra $100-$200 (15%-30%) that they will surely be asking.
View attachment 128216
Advocates of dual x3D chips might not like the conclusions. On the other hand, I wonder how the author has handled the internal game settings for SMT. As the game by default, in theory, should use 1 worker per core for 2CCD chips. It should be now possible to modify that in the options, but I never really tried to see what these are really doing. Still I wonder if anything could interfere with manually setting the affinity + whatever the special chipset driver is doing. Especially that the very last plot suggest, that by default almost all the load is rather contained on one CCD, within SMT threads.IMO enlightening bits about games versus inter-CCX traffic. Finally somebody who, rather than merely speculating about the latter effects, did some actual performance counter based monitoring.
Thats a function of the CPU to sustain high 1t boost frequencies. The CPU "hands off" the load between preferred cores to allow cores to rest & cool while others take up the load. Max frequency is sustained much longer by doing this. The algorithm is so efficient that there is basically no perf loss from doing it. This has been the case since at least Zen 2 on the AMD side.what is easily observable during any bench + hwinfo is that the boost core changes every second
t1: core 13 5ghz
t2: core 6 5ghz
t3: core 7 + 10 5ghz
.
.
. etc. not efficient
the assumption is, scheduler throws too much work over random cores, waste
I'd like to have seen the Granite Ridge parts tested in eco mode.A few very interesting benchmarks here
Besides the obvious efficiency numbers, Halo has better absolute CPU performance in quite a few ML/AI workloads, Gromacs, Palabos, GPAW and other stuff.
All the proclamations of a big efficiency advantage really seem like, for a lot of cases, it may just boil down to comparing something pushed way out of the pocket of the V/F curve against the same thing right in the pocket.From what we know, it's the same cores and the same node. There shouldn't be much of a difference in non bandwidth limited scenarios.
Do you mean that, at idle, the Strix Halo draws a similar amount of power from the wall as a desktop part despite the SoC reporting lower power consumption? Or are you saying that if you enable Eco Mode on the 9950X3D, it will draw a similar amount of power under load as the Strix Halo does under load?draws similar power from the wall, even with the big desktop idle overhead.
I have seen workloads where my 9950X3D with 88W PPT draws 190 watts at the wall and completes work slightly faster than strix halo in 120W mode, also drawing 190 watts at the wall.Do you mean that, at idle, the Strix Halo draws a similar amount of power from the wall as a desktop part despite the SoC reporting lower power consumption? Or are you saying that if you enable Eco Mode on the 9950X3D, it will draw a similar amount of power under load as the Strix Halo does under load?
47 cycles (i.e. it's the same).Has anyone checked Zen 5 L3 latency vs Zen 4 btw?
does the mesh run at the same frequency as the ring in previous gen? The ring boosting algo for desktop is IIRC ring frequency = frequency of highest boosting core, and in mobile it's some specific ratio of the highest boosting core?47 cycles (i.e. it's the same).
Yeah.does the mesh run at the same frequency as the ring in previous gen?
It's always cclk for the ring.The ring boosting algo for desktop is IIRC ring frequency = frequency of highest boosting core, and in mobile it's some specific ratio of the highest boosting core?
Kinda weird, my mini pc with the same cooler that most of the other ones have never throttles. It looked like frameworks heatsink was going to be better than that cooler that's making the rounds in the other designs.![]()
Review: Framework Desktop is a mash-up of a regular desktop PC and the Mac Studio
Size matters most for Framework’s first stab at a desktop workstation/gaming PC.arstechnica.com
Good review. The Framework included cooler isn’t that good other than that looks good.
This is a fatal flaw with LPDDR5X. Sure, when on battery, it should run as-is but when on AC power, it should switch to low latency power burning mode. Always conserving energy was just a bad engineering decision. It badly needs a turbo mode.maybe the incredibly high memory latency from the LPDDR5X is at fault.