1. Computers
  2. Display Drivers
  3. Graphics Cards
  4. Memory
  5. Motherboards
  6. Processors
  7. Software
  8. Storage
  9. Operating Systems


Facebook RSS Twitter Twitter Google Plus


Phoronix Test Suite

OpenBenchmarking.org

Multi-Core Scaling Performance Of AMD's Bulldozer

Michael Larabel

Published on 26 October 2011
Written by Michael Larabel
Page 1 of 7 - 20 Comments

There has been a lot of discussion in the past two weeks concerning AMD's new FX-Series processors and the Bulldozer architecture. In particular, with the Bulldozer architecture consisting of "modules" in which each has two x86 engines, but share much of the rest of the processing pipeline with their sibling engine; as such, the AMD FX-8150 eight-core CPU only has four modules. In this article is a look at how well the Bulldozer multi-core performance scales when toggling these different modules. The multi-core scaling performance is compared to AMD's Shanghai, Intel's Gulftown and Sandy Bridge processors.

Each Bulldozer module consists of two x86 out-of-order processing engines, two 128-bit FMAC units, and two integer cores, but shares the fetch/decode stage, the floating-point scheduler, the L2 cache, and other parts of the module. Some have loosely compared this to Intel's Hyper Threading technology. Below are slides provided by AMD that detail the AMD Bulldozer model.



In the Linux benchmarks of the AMD FX-8150 that were published this past Monday on Phoronix, the multi-core performance of the eight-core Bulldozer was shown to be comparable to that of Intel's Sandy Bridge (Core i5 2500K) and Gulftown (Core i7 970, Core i7 990X) CPUs in some of the workloads. Today's results are a new set of numbers when running the very multi-threaded-friendly Linux benchmarks and controlling the number of modules/cores that are enabled.

The UEFI on the ASUS Crosshair V Formula motherboard, which was part of the Bulldozer kit sent over by AMD, allows enabling/disabling the individual cores of the Bulldozer CPU. The multi-threaded benchmarks were run with one, two, four, six, and eight core/thread configurations. When testing with four or less, it was ensured that each core enabled was to its own module and not shared. Likewise, with the comparative Intel results, each physical core was allotted first before enabling the Hyper Threading. For the motherboards/CPUs that don't support the individual toggling of cores, the core count was limited in the Linux kernel by using the "maxcpus=" kernel option, which limits the number of cores that are exposed to the operating system.

<< Previous Page
1
Latest Linux Hardware Reviews
  1. A Walkthrough Of The New 32 System Open-Source Linux Benchmarking Test Farm
  2. Habey MITX-6771: Mini-ITX Board With Quad-Core J1900 Bay Trail
  3. OCZ Vector 150 SSD On Linux
  4. Noctua i4 CPU Cooler: Great For Cooling High-End LGA-2011v3 CPUs
Latest Linux Articles
  1. AMD Kaveri: Open-Source Radeon Gallium3D vs. Catalyst 14.12 Omega Driver
  2. 12-Way AMD Catalyst 14.12 vs. NVIDIA 346 Series Linux GPU Comparison
  3. AMD Catalyst 14.12 Omega Driver Brings Mixed Results For Linux Users
  4. 6-Way Winter 2014 Linux Distribution Comparison
Latest Linux News
  1. Intel Skylake Audio Support For Linux 3.19
  2. After 10+ Years, NetworkManager Reaches v1.0
  3. VDPAU Updated To v0.9
  4. An Open Hardware Random Number Generator Proposed
  5. LLVM 3.6 Will Be Branched Next Month
  6. Opera Browser Puts Out Linux Updates For The Holidays
  7. GNOME Shell 3.15.3 Adds Support For High-Contrast Themes
  8. Linux 3.19: ThinkPad Muting Redone, New Dell Backlight Support, Acer Is Banging
  9. KVM Drops Support For IA64 While Adding Various x86 Improvements
  10. GCC 4.8.4 Officially Released
Latest Forum Discussions
  1. XLennart: A Game For Systemd Haters With Nothing Better To Do
  2. Need some hand holding with upgrading xserver
  3. Debian init discussion in Phoenix Wright format
  4. The New SuperTuxKart Looks Better, But Can Cause GPU/Driver Problems
  5. FPS capped on Linux (AMD fglrx drivers)
  6. Are there an app using HSA ?
  7. Bench specific mount point
  8. Tool for measuring FPS in games