>Scheduling in Windows is fine Meanwhile: >Games that do their own thread scheduling instead of relying on Windows to do it get a 35%+ performance increase
As a programmer, this shit pisses me off. This expectation that hundreds of developers need to patch thousands of games instead of Windows patching once.
If Windows tried to keep all the threads of an application on one CCX, and only cross them over to another CCX. Currently, Windows tries to balance the software threads each across the main hardware threads, and keeping the SMT ones lightly loaded, which means crossing CCX. Nearly every game sees performance improvements by instead using the SMT threads of the same CCX instead of balancing load onto the second CCX. There are games that can use all 8 cores and further increase performance by managing thread scheduling to tell the scheduler which threads ought to go on the other CCX, but the vast majority of games work fine when running on one CCX, thus that should clearly be the default things that work and management should only be needed for heavily intensive applications.
Most game developers are too incompetent to do their own thread scheduling like F1 2016 and Mafia III, and aren't going to patch this shit. And AMD takes the fall for Microsoft.
Huge PR blunder by AMD. The worst they should have said is "Windows is treating SMT fine, but we are investigating other issues". Instead they said there are NO problems with the Windows scheduler, which is 100% proven to be false.
Thomas Thomas
what the fuck, that video difference was 70% in some places
Jackson Nguyen
Are there any similar issues cropping up on Linux?
Josiah Evans
it's mostly working as intended on linux AMD themselves patched it in as far as I know
James Robinson
Intel has spoken.
Too bad for them this won't help them at all in the datacenter.
Michael King
>Games that do their own thread scheduling instead of relying on Windows to do it get a 35%+ performance increase Where the ungodly fuck are you getting that? If you're referencing your image, that's not what it says at all. It literally says that the 35% difference is gained from the software being configured wrong as a fault of the third party backup system. It has literally nothing to do with windows at all and everything to do with a weird, unforseen quirk of restoring a backup.
James Richardson
MSFT is a big customer. AMD needs adoption from large companies more than consumers at this point.
Gavin Jenkins
WINDOWS SCHEDULER IS WORKING FINE REEEEEE
Yes, the same issue exists on Linux where the scheduler doesn't seem to quite understand that it should try its best to keep all the threads of an application on one CCX. The schedulers don't seem to understand the latency moving some cross CCX, though they should.
Not that no applications should use both CCX, but when a game doesn't have much workload and it can all run in one CCX, trying to then split it across two CCX incurs a lot of latency trying to use each other's shared cache when the program isn't specifically written for 2 L3 caches. No, what was fixed on Linux is just identifying which threads are SMT threads. The issue of being aware of its architecture and how there is an extra 100ns delay by crossing the CCX and being aware of most games relying on shared cache is not fixed.
So? They could have said "we're still investigating issues" to not throw MSFT under the bus but to acknowledge that something may not be working right somewhere.
Not getting that from the image. It's just a general statement. See Mafia III. See the other videos that show it 35%+ better perf using with one CCX disabled.
Henry Anderson
>it's not the OS's fault (even though it clearly is) it's game developers Fuck you, AMD.
Caleb Hall
At least on linux someone can make the scheduler for you
Jackson Hall
>down less than half a dollar >despite still being higher than where it was when Bulldozer dropped
Ryan Flores
Doesn't matter. Should be to the moon.
Logan Ortiz
>There's nothing wrong with Windows 1'
Carson Foster
Virtually the same with HPET off, peak power setting.
That is a core parking and not scheduling issue.
Windows 10 scheduler is virtually the same as Windows 7. It just core parks more aggressively.
Angel Perry
What does the high precision event timer even do?
Brandon Perez
This is why I use Linux
James Young
Linux does have the same issue of assigning threads across the CCX when it doesn't need to, though.
But I imagine it'll get fixed much faster on there.
Ian Garcia
Nothing bad is going on. Some games see gains and some games don't. It's a combination of issues including the way Win10 parks cores on balanced mode. Very few reviewers state if Win10 is set to performance mode or not.
Isaac Cook
This is about the moving threads cross CCX, not SMT, you fucktard.
Tyler Turner
Still don't understand why AMD isn't rightfully putting the blame on Microsoft. Now the plebs will only see that AMD is shit on Windows.
