The Test

To keep the review length manageable we're presenting a subset of our results here. For all benchmark results and even more comparisons be sure to use our performance comparison tool: Bench.

Motherboard: ASUS P8Z68-V Pro (Intel Z68)
ASUS Crosshair V Formula (AMD 990FX)
Hard Disk: Intel X25-M SSD (80GB)
Crucial RealSSD C300
Memory: 2 x 4GB G.Skill Ripjaws X DDR3-1600 9-9-9-20
Video Card: ATI Radeon HD 5870 (Windows 7)
Video Drivers: AMD Catalyst 11.10 Beta (Windows 7)
Desktop Resolution: 1920 x 1200
OS: Windows 7 x64

Windows 7 Application Performance

3dsmax 9

Today's desktop processors are more than fast enough to do professional level 3D rendering at home. To look at performance under 3dsmax we ran the SPECapc 3dsmax 8 benchmark (only the CPU rendering tests) under 3dsmax 9 SP1. The results reported are the rendering composite scores.

3dsmax r9—SPECapc 3dsmax 8 CPU Test

As our first heavily threaded, predominantly FP workload we see the FX-8150 come out swinging. A tangible upgrade from the Phenom II X6, the 8150 is hot on the heelds of the Core i5 2400, however it is unable to compete with the 2500K and 2600K.

Cinebench R10 & 11.5

Created by the Cinema 4D folks we have Cinebench, a popular 3D rendering benchmark that gives us both single and multi-threaded 3D rendering results.

Cinebench R10—Single Threaded Benchmark

As I alluded to earlier, single threaded performance is going to be a bit of a disappointment with Bulldozer and here you get the first dose of reality. Even considering its clock speed and Turbo Core advantage, the FX-8150 is slower than the Phenom II X6 1100T. Intel's Core i5 2500K delivers nearly 50% better single threaded performance here than the FX-8150.

Cinebench R10—Multi-Threaded Benchmark

Crank up the threads and the FX-8150 shines, finally tying the 2500K at a comparable price point.

Cinebench 11.5—Single Threaded

Even with more modern workloads, the FX-8150 isn't able to compete in single threaded speed. Here the 2500K is 44% faster.

Cinebench 11.5—Multi-Threaded

Modern multithreaded workloads however do quite well on Bulldozer. The gains over the old Phenom II X6 1100T are unfortunately not as large as we would expect them to be.

7-Zip Benchmark

7-zip Benchmark

Heavily threaded workloads obviously do well on the FX series parts, here in our 7-zip test the FX-8150 is actually faster than Intel's fastest Sandy Bridge.

PAR2 Benchmark

Par2 is an application used for reconstructing downloaded archives. It can generate parity data from a given archive and later use it to recover the archive

Chuchusoft took the source code of par2cmdline 0.4 and parallelized it using Intel’s Threading Building Blocks 2.1. The result is a version of par2cmdline that can spawn multiple threads to repair par2 archives. For this test we took a 708MB archive, corrupted nearly 60MB of it, and used the multithreaded par2cmdline to recover it. The scores reported are the repair and recover time in seconds.

Par2—Multi-Threaded par2cmdline 0.4

Once again, throw more threads at the processor and the FX-8150 can outperform the Core i5 2500K.

TrueCrypt Benchmark

TrueCrypt is a very popular encryption package that offers full AES-NI support. The application also features a built-in encryption benchmark that we can use to measure CPU performance with:

AES-128 Performance—TrueCrypt 7.1 Benchmark

Bulldozer adds AES-NI acceleration, a feature that wasn't present in the Phenom II X6. As a result the FX-8150 is among the fastest at real time AES encryption/decryption, second only to the 2600K. Intel's artificial segmentation using Hyper Threading comes back to haunt it here as the 2500K is significantly slower than the 8-threaded beast.

x264 HD 3.03 Benchmark

Graysky's x264 HD test uses x264 to encode a 4Mbps 720p MPEG-2 source. 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.

x264 HD Benchmark—1st pass—v3.03

As I mentioned earlier, the first pass of our x264 HD benchmark is a lightly threaded task. As such, the FX-8150 doesn't do very well here. Even the old Phenom II is able to inch ahead of AMD's latest. And Sandy Bridge obviously does very well.

x264 HD Benchmark—2nd pass—v3.03

The second pass is more thread heavy, allowing the FX-8150 to flex its muscle and effectively tie the 2600K for first place.

AMD also sent along a couple of x264 binaries that were compiled with AVX and AMD XOP instruction flags. We ran both binaries through our x264 test, let's first look at what enabling AVX does to performance:

x264 HD Benchmark—1st pass—v3.03—AVX Enabled

Everyone gets faster here, but Intel continues to hold onto a significant performance lead in lightly threaded workloads.

x264 HD Benchmark—2nd pass—v3.03—AVX Enabled

The standings don't change too much in the second pass, the frame rates are simply higher across the board. The FX-8150 is an x86 transcoding beast though, roughly equalling Intel's Core i7 2600K. Although not depicted here, the performance using the AMD XOP codepath was virtually identical to the AVX results.

Adobe Photoshop CS4

To measure performance under Photoshop CS4 we turn to the Retouch Artists’ Speed Test. The test does basic photo editing; there are a couple of color space conversions, many layer creations, color curve adjustment, image and canvas size adjustment, unsharp mask, and finally a gaussian blur performed on the entire image.

The whole process is timed and thanks to the use of Intel's X25-M SSD as our test bed hard drive, performance is far more predictable than back when we used to test on mechanical disks.

Time is reported in seconds and the lower numbers mean better performance. The test is multithreaded and can hit all four cores in a quad-core machine.

Adobe Photoshop CS4—Retouch Artists Speed Test

Photoshop performance improves tangibly over the Phenom II X6, unfortunately it's not enough to hang with the enthusiast Sandy Bridge parts.

Compile Chromium Test

You guys asked for it and finally I have something I feel is a good software build test. Using Visual Studio 2008 I'm compiling Chromium. It's a pretty huge project that takes over forty minutes to compile from the command line on a dual-core CPU. But the results are repeatable and the compile process will easily stress more than 8 threads on a CPU so it works for me.

Build Chromium Project—Visual Studio 2010

Our compiler test has traditionally favored heavily threaded architectures, but here we found the Phenom II X6 1100T to offer a tangible performance advantage over Bulldozer. While AMD is certainly competitive here, this is an example of one of those situations where AMD's architectural tradeoffs simply don't pay off—not without additional clock speed that is.

Excel Monte Carlo

Microsoft Excel 2007 SP1—Monte Carlo Simulation

Our final application test is another win for AMD over the Core i5 2500K. The victory is entirely a result of Intel's Hyper Threading restrictions though, the eight-thread 2600K is able to easily outperform Bulldozer. Either way, AMD delivers better performance here for less money.

Cache and Memory Performance Gaming Performance
Comments Locked

430 Comments

View All Comments

  • Mishera - Monday, October 17, 2011 - link

    Good points TekDemon. But I'll add that from what I understand, the GPU might be capable of processing huge amounts of graphic information, but might have to wait for the CPU to process certain information before it's able to continue, hence some games going only so high in graphic tests no matter what kind of GPU is put in.

    Like he said, buying a good CPU will last longer than spending that money on a really good GPU. I personally try to build a balanced system since by the time I upgrade it's a pretty big jump on all ends.
  • Snorkels - Wednesday, October 12, 2011 - link

    This and other benchmark tests are BOGUS. You are comparing apples to oranges. LiarMarks..

    This test shows non-optimized code for AMD vs optimized code for the Intel CPU.

    It does not show the actual performance of the Bulldozer CPU.

    Most software companies compile their software using Intels compiler, which creates crappy and unefficient codepaths for AMD processors.

    Compile with Open64 compiler and you get a totally different result.
  • actionjksn - Wednesday, October 12, 2011 - link

    @Snorkels If most software company's are using an Intel compiler, why would you want an AMD processor that can't utilize it properly.
  • g101 - Wednesday, October 12, 2011 - link

    Well, I'm happy that gamer children cannot understand the point of this architecture. You obviously have no concept of the architectural advantages, since it's not designed for game-playing children or completely unoptimized synthetic benchmarks.

    Bulldozer optimized and future-proofed for professional software, rather than entertainment software for children.
  • AssBall - Wednesday, October 12, 2011 - link

    "obviously have no concept of the architectural advantages"

    Enlighten us then, oh wise one.
  • guyjones - Sunday, October 16, 2011 - link

    Who exactly is the child here? Your infantile comment conveniently ignores the fact that AMD has made gigantic marketing pushes that are clearly directed at the gamer community, not to mention gaming-related sponsorship activities and marketing tie-ins. So, on the contrary, the company has made very visible and consciously-directed efforts to appeal to gamers with its products. It is totally unreasonable to now posit that BD is not directed at least in part toward that market segment.
  • Will Robinson - Wednesday, October 12, 2011 - link

    FailDozer....pretty limp performance numbers.
    Intel still rules.
  • etrigan420 - Wednesday, October 12, 2011 - link

    What an unfortunate series of events...maybe my e8400 will hold out a little longer...
  • Malih - Wednesday, October 12, 2011 - link

    before reading (and i've read all other review sites -and disappointed at AMD-, just dying to see your view on the matter) thanks for the review as always
  • xorbit - Wednesday, October 12, 2011 - link

    You are not measuring "branch prediction" performance. You are measuring misspeculation penalty (due to longer pipeline or other reasons). Nothing can "predict" random data-dependent branches.

Log in

Don't have an account? Sign up now