Video Transcoding Performance

x264 HD 5.0.1 Benchmark

We migrated to the latest verison of the x264 HD benchmark which features a much newer version of x264 and a much heavier workload. The focus here is on quality rather than speed, thus the benchmark uses a 2-pass encode and reports the average frame rate in each pass.

Windows 8 - x264 HD 5.0.1 - 1st Pass

Windows 8 - x264 HD 5.0.1 - 2nd Pass

The latest version of the x264 HD test does extremely well on Vishera. With the exception of the FX-6300, AMD is able to come away with a win at all of its price points. The FX-8350 even outperforms the Core i7 3770K.

Visual Studio 2012 - Multithreaded Compile Performance

Our compile test is back and better than ever. With a much larger and faster SSD (Samsung SSD 830, 512GB), we're able to get more consistent compile times between runs. We're now using Visual Studio 2012 to compile Mozilla's Firefox project. The compile is multithreaded however there are periods of serial operation where performance is bound by the speed of a single core. The end result is a benchmark that stresses both single and multithreaded performance. Compile times are reported in minutes elapsed.

Windows 8 - Visual Studio 2012 - Firefox Compile

It's all or nothing with Vishera. Mixed workloads that stress both single and multithreaded performance don't turn out as well on AMD's platform. With the FX-8350 AMD is able to sneak up on Sandy Bridge, but the competitive Ivy Bridge parts simply pull ahead. If there ever was a reason to fix AMD's single threaded performance, you're looking at it.

General Performance Photoshop & 3D Rendering Performance
Comments Locked

250 Comments

View All Comments

  • wwwcd - Tuesday, October 23, 2012 - link

    But the consensus is that if you're still running a Phenom 2 x6, and you don't need 8-threads and mostly play video games, it really is throwing money into the fire in order to upgrade to the FX line, Piledriver or not, unless you intend to overclock the chips to 4.8ghz+ which the Phenom 2's can't reach on air


    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

    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.

    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.

Log in

Don't have an account? Sign up now