http://www.tomshardware.com/reviews/fx-8150-zambezi-bulldozer-990fx,3043-23.html
Toms did a preview on Win8 developer, only 2 applications tested but performance did improve over Win7. It seems they actually put more threads on the same module when possible so other modules and deactivate allowing higher turbo speeds. If the updates to Win7 scheduler function the same way, I don't expect to see much if any improvement for those who disable turbo core and overclock. It is interested FX gets slightly improved performance in Win8 while Sandy Bridge lost performance.
Umm, Intel did need "special microsoft updates" when they released their original HT CPUs.
The only issue here is why AMD didn't work with Microsoft to get this released prior BD's launch. The scheduler is one of the fundamental functions of a modern OS, and while the changes needed for BD should have been relatively minor, AMD should have known that MS wasn't going to ship a hotfix to the scheduler without serious validation.
so, how in the world didn't AMD get Microsoft to implement this by launch date? Failure...
Yes it is interesting the SB looses performance .Infact its grounds for a law suite class action time again.
AMD and MS would need to work together on it, and to be sure it's correct, MS would need chip revisions guaranteed to give exactly the same performance as final production models. If they had it ready on the day of launch, they would still need to spend time testing it, and likely would not have gotten launch-equivalent CPU samples more than a few weeks ahead of the rest of the world.so, how in the world didn't AMD get Microsoft to implement this by launch date? Failure...
I think, either my principles of logic are leaving me or someone else alone. There is this "no need" posting above and a parallel thread "AMD hot fix just boosted my sandy in cinebench".It's more impressive on Intel's part that Nehalem and SB did not need any significant performance patching, than it is a black mark on AMD that BD needs it.
It's more impressive on Intel's part that Nehalem and SB did not need any significant performance patching, than it is a black mark on AMD that BD needs it.
It's more impressive on Intel's part that Nehalem and SB did not need any significant performance patching, than it is a black mark on AMD that BD needs it.
Yes it is interesting the SB looses performance .Infact its grounds for a law suite class action time again.
I think, either my principles of logic are leaving me or someone else alone. There is this "no need" posting above and a parallel thread "AMD hot fix just boosted my sandy in cinebench".
http://www.anandtech.com/bench/Product/191?vs=49
http://www.anandtech.com/bench/Product/288?vs=191
Clear improvement across the board.
http://www.anandtech.com/bench/Product/434?vs=203
http://www.tomshardware.com/reviews/fx-8150-zambezi-bulldozer-990fx,3043-20.html
Blah.
http://www.tomshardware.com/reviews/fx-8150-zambezi-bulldozer-990fx,3043-6.html
Ew.
SB was, without any fixing, far superior to Stars and Nehalem. Nehalem was far superior to Conroe and friends, and also Stars. As such, it is not in need. BD ranges from significantly worse to better than its predecessors and and competition without fixing. Typically it is the same or a bit worse, if you can't pack on the threads, and shows much more regular performance scaling under Linux than under Windows. So, it can be seen as needing some fixing.
So, it can be seen as needing some fixing.
Microsoft Pulls Down the AMD Bulldozer Multi-Threaded Patch
The patch got pulled down for unknown problems. D: Someone should re upload it elsewhere just in case someone else needs it.
I believe I've spent at least three posts ITT explaining that Windows patches for SMP performance have been business as usual since the home versions had to care about it. That I've been over.Huh? SB is the typical cpu, no big difference. BD is Very different, complicated, not the norm, new. So of course there will be teething issues. Even HT needed Winxp SP1 to work. Get over it. :whiste:
It's not. It's a new CPU that typically will not run a single thread of a desktop program as fast as the last generation, when that is an important thing to do.So a cpu's that brings nothing new technoology wise doesn't need fixing and a cpu that brings something entirely new does need fixing... how is this supposed to be illogical, bad?
They forgot to set the "check CPUID" switch so that the patch only works on AMD systems and not on Intel one's:twisted:
Don't worry, once they fix the "bug" it will be re-released just as Nvidia did with their drivers when they accidentally enabled Physx to run when AMD graphics cards were present along with an Nvidia card for the physx portion.![]()
They forgot to set the "check CPUID" switch so that the patch only works on AMD systems and not on Intel one's:twisted:
Don't worry, once they fix the "bug" it will be re-released just as Nvidia did with their drivers when they accidentally enabled Physx to run when AMD graphics cards were present along with an Nvidia card for the physx portion.![]()
Remember all those arguements if Bulldozer was a 8 core or 4 core, where an AMD Module = Intel core.
With this patch, it now shows 4 cores 8 threads doesn't it?
So better performance by treating a module as a single core.
My understanding is that this is not true. In fact it is the other way around. By treating them as real cores instead of hyperthreading it boosts performance. We'll say there are 4 cores, and an a and b thread for each core. So core 1a, core 1b, core 2a, etc. On a Intel processor the "b" cores are hyperthreaded so the scheduler will want to avoid those until last resort because 1a, 2a, 3a, and 4a are faster. In Bulldozer, if there are two threads, it is faster to put them on 1a and 1b so the other cores clock down and the turbo kicks in.