The Vishera Review: AMD FX-8350, FX-8320, FX-6300 and FX-4300 Tested
by Anand Lal Shimpi on October 23, 2012 12:00 AM ESTFinal Words
Vishera is a step in the right direction for AMD, it manages to deliver tangibly better performance than last year's disappointing FX processor without increasing power consumption. Thanks to architectural and frequency improvements, AMD delivers up to 20% better performance than last year's FX-8150 for a lower launch price, while remaining within the same thermal envelope.
AMD does manage to pull away with some very specific wins when compared to similarly priced Intel parts. Performance in the latest x264 benchmark as well as heavily threaded POV-Ray and Cinebench tests show AMD with the clear multithreaded performance advantage. Other heavily threaded integer workloads also do quite well on Vishera. The only part that didn't readily beat its Intel alternative was AMD's six-core FX-6300, the rest did extremely well in our heavily threaded tests. Look beyond those specific applications however and Intel can pull away with a significant lead. Lightly threaded applications or those whose performance depends on a mixture of single and multithreaded workloads are typically wins for Intel. The story hasn't really changed in that regard. For AMD to become competitive across the board it needs significant changes to the underlying architecture, some of which I don't know that we'll see until the 2013 - 2014 timeframe. Even then, Intel's progress isn't showing any signs of slowing.
Power consumption is also a big negative for Vishera. The CPU draws considerably more power under load compared to Ivy Bridge, or even Sandy Bridge for that matter.
Ultimately Vishera is an easier AMD product to recommend than Zambezi before it. However the areas in which we'd recommend it are limited to those heavily threaded applications that show very little serialization. As our compiler benchmark shows, a good balance of single and multithreaded workloads within a single application can dramatically change the standings between AMD and Intel. You have to understand your workload very well to know whether or not Vishera is the right platform for it. Even if the fit is right, you have to be ok with the increased power consumption over Intel as well.
Facebook
Twitter
RSS
250 Comments
View All Comments
wwwcd - Tuesday, October 23, 2012 - link
Yes, we don't neeed of 8 core/threads for gaming today, but do You have prognosis for near future?
Kisper - Tuesday, October 23, 2012 - link
Why would you upgrade for no reason other than speculation?If an advantage arises in heavily threaded games in the future, upgrade at that time. You'll get more processing power / $ spent in the future than you will at present.
CeriseCogburn - Tuesday, October 30, 2012 - link
amd fanboys are pennywise and pound foolish, so buying the amd crap now, and telling everyone it has the deranged amd furuteboy advantage, works for them !I mean really, it sucks so freaking bad, they cannot help themselves, like a crack addict they must have and promote, so heck, the last hope of the loser is telling everyone how bright they are and how on down the line in the imaginary years ahead their current pileofcrap will "truly shine!"
LOL - oh man, funny but so true.
Spunjji - Tuesday, October 23, 2012 - link
Prognosis for the near future is that having that many threads will still not be a whole lot of use for gaming. See Amdahl's law for why.Samus - Tuesday, October 23, 2012 - link
It's safe to say all programs/games going forward will take advantage of four cores or more. Battlefield 3 released LAST year and basically requires 4 cores in order to be GPU-limited (as in the game is CPU limited with just about any videocard unless you have 4 cores.c0d1f1ed - Tuesday, October 23, 2012 - link
Amdahl's Law is not a reason. There is plenty of task parallelism to exploit. The real issue is ROI, and there's two aspects to that. One is that multi-threaded development is freakishly hard. Unlike single-threaded development, you cannot know exactly what each thread is doing at any given time. You need to synchronised to make certain actions deterministic. But even then you can end up with race conditions if you're not careful. The current synchronization methods are just very primitive. Intel will fix that with Haswell. The TSX technology enables hardware lock elision and hardware transactional memory. Both will make the developer's life a lot easier, and also make synchronization more efficient.
The second aspect isn't about the costs but about the gains. It has taken quite a while for more than two cores to become the norm. So it just wasn't worth it for developers to go through all the pain of scalable fine-grained multi-threaded development if the average CPU is still only a dual-core. Haswell's TSX technology will come right in time as quad-core becomes mainstream. Also, Haswell will have phenomenal Hyper-Threading performance thanks to two nearly symmetrical sets of two integer execution units.
AMD needs to implement TSX and AVX2 sooner rather than later to stay in the market.
CeriseCogburn - Tuesday, October 30, 2012 - link
Nice post. Appreciate it.And ouch for amd once again.
surt - Tuesday, October 23, 2012 - link
No, gaming won't need that many threads in the near future either. Nobody is going to make a game demand more than 4 threads because that's what common gamer systems support.AnnihilatorX - Wednesday, October 24, 2012 - link
I disagree. Say we have a hypothetical game that support 8 threads. The overhead of over-threading in a quad core system is frankly, not very much, while it may provide improvements on people with octocore or Intel processors with hyper-threading.AnnihilatorX - Wednesday, October 24, 2012 - link
In fact, there are many games nowadays that split workload into many threads for economic simulation, background AI planning in user phase, physics, audio, graphics subthread, network management, preloading and resources management. It is just that even with the parallelism, there bound to be bottlenecks in single threading that a 8 core may not benefit at all compared to 4 cores.So I disagree, it is not about people not spending resources in making parallelism or not supporting it. It is the nature of the workload that is the determining factor.