Don't know if anyone saw it.
Here it is
http://www.anandtech.com/show/5448/the-bulldozer-scheduling-patch-tested
Here it is
http://www.anandtech.com/show/5448/the-bulldozer-scheduling-patch-tested
Ok AMD, why not just let Bulldozer be a failure and move on?
All they have is BD+n and Bobcat+n. Maybe they could invest in cache development?The more AMD tries to prove themselves with BD, the more disappointed I am. They should just scrap BD and divert their attention and resources on something worthwhile.
![]()
The more AMD tries to prove themselves with BD, the more disappointed I am. They should just scrap BD and divert their attention and resources on something worthwhile.
![]()
BD had too much cache and too little logic that actually does the work. The transistor count means nothing when they have themselves a huge cache but slow as hell. They should either put their focus more on their GPU, mobile APU or join forces with ARM and improve their presence in anything related to mobility. I think it would be very unlikely we would see BD or its future iterations taking the performance crown from Intel anytime soon.All they have is BD+n and Bobcat+n. Maybe they could invest in cache development?
Those gamers have to be certified as visually impaired. 😀At least BD is still THE CPU for gaming. Oh wait...
BD had too much cache and too little logic that actually does the work. The transistor count means nothing when they have themselves a huge cache but slow as hell. They should either put their focus more on their GPU, mobile APU or join forces with ARM and improve their presence in anything related to mobility. I think it would be very unlikely we would see BD or its future iterations taking the performance crown from Intel anytime soon.
Those gamers have to be certified as visually impaired. 😀
I remember when JFAMD argued that the windows scheduler didn't need any extra tuning for Bulldozer and it should treat all "cores" equally. Many of us argued against that, saying the scheduler should use the same principle as it does with a CPU+SMT(HT). Look who was right.......
He was right in that Bulldozer doesn't pretend to be an SMT CPU to the OS apparently. If it was designed that way, this hotfix patch wouldn't have been necessary!
Hmm, unless I missed something I think he was actually right. I mean you don't get more than a few % improvement from extra scheduler awareness. Judging from Linux results they'd be better off trying to incorporate compiler/code improvements into the Windows codebase rather than spend an inordinate amount of time on the scheduler.
Still miffed at the first iteration of BD in general. Missed targets in both fabrication and design and that's after quite a long delay from original timeline estimates.
A patch that supposedly "optimizes" the scheduler for Bulldozer architecture, yet the performance gain is only 1-2%.
Ok AMD, why not just let Bulldozer be a failure and move on?
I remember when JFAMD argued that the windows scheduler didn't need any extra tuning for Bulldozer and it should treat all "cores" equally. Many of us argued against that, saying the scheduler should use the same principle as it does with a CPU+SMT(HT). Look who was right.......
He was right in that Bulldozer doesn't pretend to be an SMT CPU to the OS apparently. If it was designed that way, this hotfix patch wouldn't have been necessary!
A patch that supposedly "optimizes" the scheduler for Bulldozer architecture, yet the performance gain is only 1-2%.
Ok AMD, why not just let Bulldozer be a failure and move on?
well, with intel content....with Haswell.
It was a 4-5% gain on a couple games. The only reason the "average" gain was 1-2% was because many of the tests were (admittedly) on workloads that either use only 1 thread or all threads, in which moving threads around won't change anything.
Would it be more impressive if Anand said "since single and 8 threaded applications shouldn't benefit from this patch, we won't test them" and the average gain was 5%?
15% of nothing is nothing.I actually think it's done more harm than good. Chances are AMD had to pay MS to develop this "hotfix" as it's their hardware which changed things.
If the hotfix had given a big bump, like 15% or more than it certainly would have been worth while. When their internal testing came out around 1-2%, someone should have thought that this isn't worth it and people will just laugh at it when it's released.
15% of nothing is nothing.