• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

AMD Introduces Dynamic Local Mode for Threadripper: up to 47% Performance Gain

This whole comment seems wholly pointless so I thought I'd add another one.

He has a negative overtone which makes me wonder. By the way who are you, never seen you before till now?
 
So in local mode, how low can the latency go in AIDA 64? Intel can already go sub-40ns.
 
So in local mode, how low can the latency go in AIDA 64? Intel can already go sub-40ns.

Being an announcement and not a finished deal we are unsure at the moment, just wait and see.
 
AMD is still, what, 10% slower on IPC? That's still a win for Intel. Also, notice that I said Intel would win, not by how much. That depends on specific cases which is outside the scope of my comment.
It's less than 10%.
Interestingly enough, as diligent as HardOCP is testing Intel's IPC, they seem to have missed Zen completely. Still, I could find:
https://www.sweclockers.com/test/24701-intel-core-i9-7980xe-skylake-x/19#content

and if you don't mind looking at slightly older hardware:
https://forums.anandtech.com/threads/ryzen-strictly-technical.2500572/#post-38770109

So in local mode, how low can the latency go in AIDA 64? Intel can already go sub-40ns.
I don't think this is supposed to lower latency. Just to move threads that need lower latency to the cores that are connected to RAM.
 
Last edited:
I already did this manually for games that needed it (gta 5). Kind of cool they added a quick button for it.

I would like to still see some bios improvements the downcore modes for the 2990wx are silly on my asrock board. I want to just tell it to run two module mode and basically boot like a 2950x, but that isn't a thing unless I use ryzen master which kills my oc and I have to oc through windows which isn't the same for me.
 
Well if this was inbuilt and didn't need software ill buy a AMD CPU.
 
Well if this was inbuilt and didn't need software ill buy a AMD CPU.
I very much doubt that is what makes or breaks a decision to go for an AMD CPU.
 
No reason to celebrate, this is patchwork to deal with the flawed design of 2970WX/2990WX, they should have worked better than this in the first place.

So AMD can fix what Microsoft can't fix in the scheduler.
Why should Microsoft redesign their kernel to fit a flawed CPU design?
AMD is at fault for outfitting 2970WX/2990WX with two "crippled" dies. When AMD needs to make a program to manipulate the running threads in real time, then something is not right.

While 2950X(16-core) is an okay product, 2970WX/2990WX only scales well for certain workloads, more server workloads rather than workstation. AMD would have to do better for Zen 2 Threadrippers.
 
No reason to celebrate, this is patchwork to deal with the flawed design of 2970WX/2990WX, they should have worked better than this in the first place.


Why should Microsoft redesign their kernel to fit a flawed CPU design?
AMD is at fault for outfitting 2970WX/2990WX with two "crippled" dies. When AMD needs to make a program to manipulate the running threads in real time, then something is not right.

While 2950X(16-core) is an okay product, 2970WX/2990WX only scales well for certain workloads, more server workloads rather than workstation. AMD would have to do better for Zen 2 Threadrippers.

You sound like you're a paid puppet to say crap like that. Remember one thing this is a new architecture. There is no flaw in the design it's just that anytime a brand new processor comes out there's ajustments that need to be made to the operating system itself. But Microsoft too darn lazy to do it.

Where there is no problem in Linux. So you are telling me that open software foundations are able to fix the problems yeta multi-billion-dollar company cannot?

I will tell you what is flawed that's Intel processors due to Spectre and meltdown, that bios updates and winblows patches were released that crippled their performance even further. Yet Microsoft Tried to force in those patches on AMD Rigs, but won't fix scheduler flaws?

Go back into your cave and hibernate.
 
Last edited:
No reason to celebrate, this is patchwork to deal with the flawed design of 2970WX/2990WX, they should have worked better than this in the first place.


Why should Microsoft redesign their kernel to fit a flawed CPU design?
AMD is at fault for outfitting 2970WX/2990WX with two "crippled" dies. When AMD needs to make a program to manipulate the running threads in real time, then something is not right.

While 2950X(16-core) is an okay product, 2970WX/2990WX only scales well for certain workloads, more server workloads rather than workstation. AMD would have to do better for Zen 2 Threadrippers.
Eh, it's not crippled any more than a core with HT on top.
It's an asymmetric design in a world that's not used to that. To that end, AMD could have probably done a better job and ensured everything was worked out before launch. That aside, if you understand the limitations and you really need all those cores*, these CPUs can deliver.

*admittedly a sliver of the market as a whole, but HEDT never catered to anything but
 
You sound like you're a paid puppet to say crap like that. Remember one thing this is a new architecture. There is no flaw in the design it's just that anytime a brand new processor comes out there's ajustments that need to be made to the operating system itself. But Microsoft too darn lazy to do it.

Where there is no problem in Linux. So you are telling me that open software foundations are able to fix the problems yeta multi-billion-dollar company cannot?

I will tell you what is flawed that's Intel processors due to Spectre and meltdown, that bios updates and winblows patches were released that crippled their performance even further. Yet Microsoft Tried to force in those patches on AMD Rigs, but won't fix scheduler flaws?

Go back into your cave and hibernate.
do amd cpus get a performance hit form those updates too ?
 
You sound like you're a paid puppet to say crap like that. Remember one thing this is a new architecture. There is no flaw in the design it's just that anytime a brand new processor comes out there's ajustments that need to be made to the operating system itself. But Microsoft too darn lazy to do it.
Stop making excuses, this has nothing to do with this being a new architecture, only 2970WX/2990WX have scaling issues this severe. Claiming that Microsoft should make a specialized kernel to work around the design flaws of these two CPU models is ridiculous, even if Microsoft had all the money in the world. No amount of software workarounds will be a complete solution to this fault.

Eh, it's not crippled any more than a core with HT on top.
Nope. Two of the dies have to go through two other dies to access memory, which is a major bottleneck. As seen in a number of benchmarks, the 32-core may even perform worse than the 16-core.
 
Nope. Two of the dies have to go through two other dies to access memory, which is a major bottleneck. As seen in a number of benchmarks, the 32-core may even perform worse than the 16-core.

Yes and in the case of HT, two cores compete not only for the same memory bandwidth, but also for the same prefetch and decode hardware. In both cases, some flows work better, some work worse with these enabled.
 
Stop making excuses, this has nothing to do with this being a new architecture, only 2970WX/2990WX have scaling issues this severe. Claiming that Microsoft should make a specialized kernel to work around the design flaws of these two CPU models is ridiculous, even if Microsoft had all the money in the world. No amount of software workarounds will be a complete solution to this fault.


Nope. Two of the dies have to go through two other dies to access memory, which is a major bottleneck. As seen in a number of benchmarks, the 32-core may even perform worse than the 16-core.

As I said before you're a paid puppet and I ain't making no excuses you're the one that's making excuses and talking crap.

Go back to your Intel threads
 
No reason to celebrate, this is patchwork to deal with the flawed design of 2970WX/2990WX, they should have worked better than this in the first place.


Why should Microsoft redesign their kernel to fit a flawed CPU design?
AMD is at fault for outfitting 2970WX/2990WX with two "crippled" dies. When AMD needs to make a program to manipulate the running threads in real time, then something is not right.

While 2950X(16-core) is an okay product, 2970WX/2990WX only scales well for certain workloads, more server workloads rather than workstation. AMD would have to do better for Zen 2 Threadrippers.
Stop making excuses, this has nothing to do with this being a new architecture, only 2970WX/2990WX have scaling issues this severe. Claiming that Microsoft should make a specialized kernel to work around the design flaws of these two CPU models is ridiculous, even if Microsoft had all the money in the world. No amount of software workarounds will be a complete solution to this fault.


Nope. Two of the dies have to go through two other dies to access memory, which is a major bottleneck. As seen in a number of benchmarks, the 32-core may even perform worse than the 16-core.
While it's not my favourite design, I don't think you can claim it's flawed. As I said in a previous post above, a monolithic design like Intel's gives better performance without those latency drawbacks, but AMD's design is much easier to scale and bring to market. I'm sure later versions of the CPU will have a better version of Infinity Fabric, too.
 
Yes and in the case of HT, two cores compete not only for the same memory bandwidth, but also for the same prefetch and decode hardware. In both cases, some flows work better, some work worse with these enabled.
SMT(like HT) are not two cores in any way, it can't be compared with having fast and "slow" real cores.
While it's not my favourite design, I don't think you can claim it's flawed. As I said in a previous post above, a monolithic design like Intel's gives better performance without those latency drawbacks, but AMD's design is much easier to scale and bring to market. I'm sure later versions of the CPU will have a better version of Infinity Fabric, too.

Epyc doesn't suffer the same drawbacks. I'm not criticizing AMD's design of multiple dies, but putting crippled dies on two products.
 
do amd cpus get a performance hit form those updates too ?
The only possible hit would be during the threads migration. But that would take well under a second, so you wouldn't spot it in benchmarks. A minor hiccup is what I'd expect to see in a worst case scenario.
 
do amd cpus get a performance hit form those updates too ?

Yes do because they are originally designed for Intel had them intentionally try to cripple thoew systems because Microsoft tries to slip them in without you knowing.
 
Last edited:
Yes do because they are originally designed for Intel had them intentionally try to cripple tosw systems because Microsoft tries to slip them in without you knowing.
well that sucks.
is the hit that big ?
 
Epyc doesn't suffer the same drawbacks. I'm not criticizing AMD's design of multiple dies, but putting crippled dies on two products.
Ok great, so when you talk about crippled dies, do you mean disabled dies to make a lower end processor? If so, why is that a bad thing? It just means that they can still sell lower end products through binning.
 
Ok great, so when you talk about crippled dies, do you mean disabled dies to make a lower end processor? If so, why is that a bad thing? It just means that they can still sell lower end products through binning.
(facepalm)
No, not at all. Where do you get this from? Two dies on 2970WX/2990WX have to go through the Infinity Fabric to access memory, which causes significant latency. Many workloads are latency sensitive, and this only gets worse when using multiple applications at once. AMD could have made Threadripper without these limitations, but perhaps not on this socket.
I thought this was a tech forum…
 
(facepalm)
No, not at all. Where do you get this from? Two dies on 2970WX/2990WX have to go through the Infinity Fabric to access memory, which causes significant latency. Many workloads are latency sensitive, and this only gets worse when using multiple applications at once. AMD could have made Threadripper without these limitations, but perhaps not on this socket.
I thought this was a tech forum…

Yes this is a techforum however you're a chronic troller of AMD threads.

As i said before gtho, go back to your intel threads.
 
This is for the new Threadripper 2000x series though isn't it? This won't work on the earlier 1000x series Threadripper or standard Ryzen.
 
This is for the new Threadripper 2000x series though isn't it? This won't work on the earlier 1000x series Threadripper or standard Ryzen.

Send AMD An email to the developers of ryzen master, they would know
 
Back
Top