- Joined
- May 18, 1997
- Messages
- 55,510
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Well, I have been pointing this out for two months now. Premeire rolled out a new version this week, about to test it. However, it seemed to greatly hobble another CPU I happened to be reviewing at the moment.Seems like that would be a software issue not utilizing the cores available, should be a easy fix.
I would think this is the problem or part of the problem since the 2950X does not exhibit this. You would think after a couple months AMD would have addressed the issue that is specific to workstation usage.It looks like the 2990WX seems to using be too much those cores that only access memory thru the infinity fabric. Can you try blocking it away from those cores (cores 8-15 & 24-31 appear to be those cores with no direct memory access) with process lasso' core affinity and giving it a shot?
Asked that last week. Got no real answers. I do have the software on the way.Do you think this is something Dynamic Local Mode may help with?
Conspiracy or laziness? Or avoiding fix because of less market penetration?
I speculated before TR2 launch that there might be some workloads where there might be scaling issues due to way memory is accessed on the CCX's. Likely due to a scheduling issue being unaware of which CCX's have direct access.
Of course this is the issue and it can be optimised around, so e.g. it should be no slower than a 2 die TR configuration (2950) but it doesn't explain why it has regressed further in performance with an update now...I speculated before TR2 launch that there might be some workloads where there might be scaling issues due to way memory is accessed on the CCX's. Likely due to a scheduling issue being unaware of which CCX's have direct access.
So cutting the affinity down to the cores that touch the memory, basically turning the 2990WX into a 2950X brings it somewhat back into parity with the 2950X by 10%.Kyle try process lasso
I use it and LOVE it.....
If I had purchased one for myself already, I would. Alas I only have one to test with and I do not feel like shelling out the $1800 for the one I was going to buy to use primarily with Premiere Pro.Kyle trade me your 2990wx I'll ship you my 2950x and well both be happy. Ha ha
That's exactly what the 'Dynamic local mode' does, it prioritizes memory-hungry threads to CCX clusters with direct memory access.
One would wonder if it would have been better to run one memory channel per die like 1+1+1+1 instead of the 2+0+2+0 system they have. Amazing chip, shitty software integration.
Of course this is the issue and it can be optimised around, so e.g. it should be no slower than a 2 die TR configuration (2950) but it doesn't explain why it has regressed further in performance with an update now...
Still working on this with AMD and now Adobe is getting brought in.Well this all seems juicy! Tell us more!
I am not so sure there are not some things "broken" in PPro, but I am going to redo my workload to get rid of some irregularities and will start out simple and see how the numbers line up again. One that is for sure, is that AMD has been able to reproduce some of my results in their lab with my PPro project that I sent over to them. So we all know that I am not crazy now....at least about this.Kyle. A man of action. If I could give you a fist bump all the way from Sydney, I would.