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

ATI Open vs. Closed-Source Performance

Michael Larabel

Published on 4 November 2007
Written by Michael Larabel
Page 1 of 4 - 2 Comments

This past Friday we had delivered benchmarks comparing the performance of the open-source Radeon driver against the new closed-source fglrx driver from AMD. These benchmarks had just looked at the AIGLX performance when using Compiz on an Ubuntu 7.10 desktop. In all of the benchmarks except one, the fglrx driver had carried a staggering lead over the open-source competition. In addition to these Compiz benchmarks, on the same system we had also ran some additional benchmarks to see for gaming and 2D rendering how the two ATI Linux drivers compare.

The system once again was running Ubuntu 7.10 "Gutsy Gibbon" with the Linux 2.6.22 kernel and X server 1.3, but with these benchmarks, the Compiz effects were disabled during testing. The hardware included a PCI Express ATI Radeon X800XL 256MB graphics card, Intel Pentium D 820 (2.80GHz dual-core), 2GB of DDR3-1333 memory, and an ASUS P5E3 Deluxe (Intel X38) motherboard. We had used Enemy Territory and GtkPerf as our vehicle for benchmarking the two drivers, since both benchmarks are compatible with the current Radeon driver. The ATI driver used was fglrx 8.42.3.

The last time we had compared these two drivers was back in February with X.Org 7.2: ATI Open v. Closed Drivers. During that examination, Fedora 7 Test 1 was used with the fglrx 8.34 driver, and of course, that was running off AMD's old driver code-base. Mesa and the Radeon driver have also seen a few improvements since that point. Most notably, Mesa 7.0 does contain a number of improvements. In those earlier benchmarks, the Radeon X800XL with the open-source driver was over twice as slow as the X800XL with the fglrx 8.34 driver. However, in these benchmarks we had not looked at the 2D GTK+ performance.

For our Enemy Territory benchmarks, we had completed the timed-demo tests with a resolution of 800 x 600 and 1280 x 1024. For the GtkPerf tests, which as the name implies tests the GTK+ performance, we had reported the results for GtkComboBox, GtkCheckButton, GtkTextView - Add Text, GtkDrawingArea - Text, and the total time needed to run all GtkPerf tests. Each GtkPerf test was run 1,000 times.

<< Previous Page
1
Latest Linux Hardware Reviews
  1. CompuLab Intense-PC2: An Excellent, Fanless, Mini PC Powered By Intel's i7 Haswell
  2. From The Atom 330 To Haswell ULT: Intel Linux Performance Benchmarks
  3. AMD Radeon R9 285 Tonga Performance On Linux
  4. Apotop Wi-Copy
Latest Linux Articles
  1. AMD Moves Forward With Unified Linux Driver Strategy, New Kernel Driver
  2. MSI: Update Your BIOS From The Linux Desktop
  3. NVIDIA vs. AMD 2D Linux Drivers: Catalyst Is Getting Quite Good At 2D
  4. 15-Way GPU Comparison With Mesa 10.3 + Linux 3.17
Latest Linux News
  1. Phoronix Test Suite 5.4 M3 Is Another Hearty Update
  2. GParted 0.20 Improves Btrfs Support
  3. EXT4 In Linux 3.18 Has Clean-ups, Bug Fixes
  4. Emacs 24.4 Has Built-In Web Browser, Improved Multi-Monitor Support
  5. NVIDIA's NVPTX Support For GCC Is Close To Being Merged
  6. KDE's KWin On Wayland Begins Using Libinput
  7. Khronos Releases OpenVX 1.0 Specification
  8. Linux Kernel Working Towards GNU11/C11 Compatibility
  9. Ubuntu 15.04 Is Codenamed After A Monkey: Vivid Vervet
  10. Following GCC, Clang Looks To Default To C11
Latest Forum Discussions
  1. Updated and Optimized Ubuntu Free Graphics Drivers
  2. Users/Developers Threatening Fork Of Debian GNU/Linux
  3. HOPE: The Ease Of Python With The Speed Of C++
  4. Bye bye BSD, Hello Linux: A Sys Admin's Story
  5. NVIDIA Presents Its Driver Plans To Support Mir/Wayland & KMS On Linux
  6. AMD Is Restructuring Again, Losing 7% Of Employees
  7. Open-Source AMD Fusion E-350 Support Takes A Dive
  8. Upgrade to Kaveri, very slow VDPAU performance