Category Archive
The following is a list of all entries from the Benchmarks category. Noteworthy entries are filed topmost.
Back at the beginning of December I posted a Geekbench comparison featuring a number of current (and not-so-current) processors. For those of you keeping score at home, you might’ve noticed that the comparison only looked at non-overclocked processors. Since Geekbench is popular with the overclocking crowd, I thought it’d be interesting to look at non-overclocked and overclocked results for some of the more popular processors in the Geekbench Result Browser database.
Setup
Much like December’s Geekbench comparison, I’ve collected results from the Geekbench Result Browser database for the 32-bit Windows version of Geekbench running on systems with at least 512MB of RAM.
Instead of averaging the overall scores for each processor (as was done in previous comparisons), I’ve plotted each score for each processor in a graph that shows the effect of processor frequency on Geekbench score (each processor gets its own graph). Higher scores are better.
Results





Conclusion
I’m not at all surprised to see that Geekbench scores for the same model of processor tend to increase with processor speed; after all, Geekbench is a processor benchmark! I’m also not surprised to see that Geekbench scores don’t just depend on processor frequency; looking at the graphs it’s clear that other factors play a role (such as memory configuration).
What is interesting is the clusters of results at certain frequencies for the Core 2 Duo processors. There’s a cluster of results around the stock frequency, and a second cluster around a higher frequency; I wonder if this second cluster shows the overclocking limit of each particular Core 2 Duo processor (without resorting to exotic cooling systems).
So, if you want to improve your Geekbench score, the most obvious way to do it is by overclocking your processor. However, as the graphs show, there are other, less obvious ways to do it, too (such as investing in faster memory).
As we’ve known for a while now, it’s possible to upgrade the processors in the Mac Pro. Now that quad-core Xeon processors are available now, some enterprising Mac user has gone out and upgraded the processors in their stock Mac Pro from two dual-core Xeons to two quad-core Xeons, and run Geekbench on their new eight-core Mac Pro. I thought it’d be interesting to see how the performance of this eight-core Mac Pro compares to a couple of the stock four-core Mac Pros.
Setup
Mac Pro (Quad-Core Xeon @ 2.33GHz)
- Two Intel Xeon E5345 quad-core processors @ 2.33GHz
- 4096MB RAM
- Mac OS X 10.4.8
- Geekbench 2006 64-bit (Build 242)
Mac Pro (Dual-Core Xeon @ 3.00GHz)
- Two Intel Xeon 5160 dual-core processors @ 3.00GHz
- 4096MB RAM
- Mac OS X 10.4.8
- Geekbench 2006 64-bit (Build 242)
Mac Pro (Dual-Core Xeon @ 2.66GHz)
- Two Intel Xeon 5150 dual-core processors @ 2.66GHz
- 4096MB RAM
- Mac OS X 10.4.8
- Geekbench 2006 64-bit (Build 242)
I’m reporting the baseline score, rather than the raw score, for each benchmark (where a score of 100 is the score a Power Mac G5 1.6GHz would receive). Higher is better.
Overall Score
Mac Pro (Eight Cores @ 2.33GHz)
Mac Pro (Four Cores @ 3.00GHz)
Mac Pro (Four Cores @ 2.66GHz)
Emulate 6502 (single-threaded scalar)
Mac Pro (Eight Cores @ 2.33GHz)
Mac Pro (Four Cores @ 3.00GHz)
Mac Pro (Four Cores @ 2.66GHz)
Emulate 6502 (multi-threaded scalar)
Mac Pro (Eight Cores @ 2.33GHz)
Mac Pro (Four Cores @ 3.00GHz)
Mac Pro (Four Cores @ 2.66GHz)
Blowfish (single-threaded scalar)
Mac Pro (Eight Cores @ 2.33GHz)
Mac Pro (Four Cores @ 3.00GHz)
Mac Pro (Four Cores @ 2.66GHz)
Blowfish (multi-threaded scalar)
Mac Pro (Eight Cores @ 2.33GHz)
Mac Pro (Four Cores @ 3.00GHz)
Mac Pro (Four Cores @ 2.66GHz)
bzip2 Compress (single-threaded scalar)
Mac Pro (Eight Cores @ 2.33GHz)
Mac Pro (Four Cores @ 3.00GHz)
Mac Pro (Four Cores @ 2.66GHz)
bzip2 Compress (multi-threaded scalar)
Mac Pro (Eight Cores @ 2.33GHz)
Mac Pro (Four Cores @ 3.00GHz)
Mac Pro (Four Cores @ 2.66GHz)
bzip2 Decompress (single-threaded scalar)
Mac Pro (Eight Cores @ 2.33GHz)
Mac Pro (Four Cores @ 3.00GHz)
Mac Pro (Four Cores @ 2.66GHz)
bzip2 Decompress (multi-threaded scalar)
Mac Pro (Eight Cores @ 2.33GHz)
Mac Pro (Four Cores @ 3.00GHz)
Mac Pro (Four Cores @ 2.66GHz)
Floating Point Performance
Mandelbrot (single-threaded scalar)
Mac Pro (Eight Cores @ 2.33GHz)
Mac Pro (Four Cores @ 3.00GHz)
Mac Pro (Four Cores @ 2.66GHz)
Mandelbrot (multi-threaded scalar)
Mac Pro (Eight Cores @ 2.33GHz)
Mac Pro (Four Cores @ 3.00GHz)
Mac Pro (Four Cores @ 2.66GHz)
Dot Product (single-threaded scalar)
Mac Pro (Eight Cores @ 2.33GHz)
Mac Pro (Four Cores @ 3.00GHz)
Mac Pro (Four Cores @ 2.66GHz)
Dot Product (multi-threaded scalar)
Mac Pro (Eight Cores @ 2.33GHz)
Mac Pro (Four Cores @ 3.00GHz)
Mac Pro (Four Cores @ 2.66GHz)
Dot Product (single-threaded vector)
Mac Pro (Eight Cores @ 2.33GHz)
Mac Pro (Four Cores @ 3.00GHz)
Mac Pro (Four Cores @ 2.66GHz)
Dot Product (multi-threaded vector)
Mac Pro (Eight Cores @ 2.33GHz)
Mac Pro (Four Cores @ 3.00GHz)
Mac Pro (Four Cores @ 2.66GHz)
JPEG Compress (single-threaded scalar)
Mac Pro (Eight Cores @ 2.33GHz)
Mac Pro (Four Cores @ 3.00GHz)
Mac Pro (Four Cores @ 2.66GHz)
JPEG Compress (multi-threaded scalar)
Mac Pro (Eight Cores @ 2.33GHz)
Mac Pro (Four Cores @ 3.00GHz)
Mac Pro (Four Cores @ 2.66GHz)
JPEG Decompress (single-threaded scalar)
Mac Pro (Eight Cores @ 2.33GHz)
Mac Pro (Four Cores @ 3.00GHz)
Mac Pro (Four Cores @ 2.66GHz)
JPEG Decompress (multi-threaded scalar)
Mac Pro (Eight Cores @ 2.33GHz)
Mac Pro (Four Cores @ 3.00GHz)
Mac Pro (Four Cores @ 2.66GHz)
Read Sequential (single-threaded scalar)
Mac Pro (Eight Cores @ 2.33GHz)
Mac Pro (Four Cores @ 3.00GHz)
Mac Pro (Four Cores @ 2.66GHz)
Read Sequential (multi-threaded scalar)
Mac Pro (Eight Cores @ 2.33GHz)
Mac Pro (Four Cores @ 3.00GHz)
Mac Pro (Four Cores @ 2.66GHz)
Write Sequential (single-threaded scalar)
Mac Pro (Eight Cores @ 2.33GHz)
Mac Pro (Four Cores @ 3.00GHz)
Mac Pro (Four Cores @ 2.66GHz)
Write Sequential (multi-threaded scalar)
Mac Pro (Eight Cores @ 2.33GHz)
Mac Pro (Four Cores @ 3.00GHz)
Mac Pro (Four Cores @ 2.66GHz)
Stdlib Allocate (single-threaded scalar)
Mac Pro (Eight Cores @ 2.33GHz)
Mac Pro (Four Cores @ 3.00GHz)
Mac Pro (Four Cores @ 2.66GHz)
Stdlib Allocate (multi-threaded scalar)
Mac Pro (Eight Cores @ 2.33GHz)
Mac Pro (Four Cores @ 3.00GHz)
Mac Pro (Four Cores @ 2.66GHz)
Stdlib Write (single-threaded scalar)
Mac Pro (Eight Cores @ 2.33GHz)
Mac Pro (Four Cores @ 3.00GHz)
Mac Pro (Four Cores @ 2.66GHz)
Stdlib Write (multi-threaded scalar)
Mac Pro (Eight Cores @ 2.33GHz)
Mac Pro (Four Cores @ 3.00GHz)
Mac Pro (Four Cores @ 2.66GHz)
Stdlib Copy (single-threaded scalar)
Mac Pro (Eight Cores @ 2.33GHz)
Mac Pro (Four Cores @ 3.00GHz)
Mac Pro (Four Cores @ 2.66GHz)
Stdlib Copy (multi-threaded scalar)
Mac Pro (Eight Cores @ 2.33GHz)
Mac Pro (Four Cores @ 3.00GHz)
Mac Pro (Four Cores @ 2.66GHz)
Stream Copy (single-threaded scalar)
Mac Pro (Eight Cores @ 2.33GHz)
Mac Pro (Four Cores @ 3.00GHz)
Mac Pro (Four Cores @ 2.66GHz)
Stream Copy (multi-threaded scalar)
Mac Pro (Eight Cores @ 2.33GHz)
Mac Pro (Four Cores @ 3.00GHz)
Mac Pro (Four Cores @ 2.66GHz)
Stream Copy (single-threaded vector)
Mac Pro (Eight Cores @ 2.33GHz)
Mac Pro (Four Cores @ 3.00GHz)
Mac Pro (Four Cores @ 2.66GHz)
Stream Copy (multi-threaded vector)
Mac Pro (Eight Cores @ 2.33GHz)
Mac Pro (Four Cores @ 3.00GHz)
Mac Pro (Four Cores @ 2.66GHz)
Stream Scale (single-threaded scalar)
Mac Pro (Eight Cores @ 2.33GHz)
Mac Pro (Four Cores @ 3.00GHz)
Mac Pro (Four Cores @ 2.66GHz)
Stream Scale (multi-threaded scalar)
Mac Pro (Eight Cores @ 2.33GHz)
Mac Pro (Four Cores @ 3.00GHz)
Mac Pro (Four Cores @ 2.66GHz)
Stream Scale (single-threaded vector)
Mac Pro (Eight Cores @ 2.33GHz)
Mac Pro (Four Cores @ 3.00GHz)
Mac Pro (Four Cores @ 2.66GHz)
Stream Scale (multi-threaded vector)
Mac Pro (Eight Cores @ 2.33GHz)
Mac Pro (Four Cores @ 3.00GHz)
Mac Pro (Four Cores @ 2.66GHz)
Stream Add (single-threaded scalar)
Mac Pro (Eight Cores @ 2.33GHz)
Mac Pro (Four Cores @ 3.00GHz)
Mac Pro (Four Cores @ 2.66GHz)
Stream Add (multi-threaded scalar)
Mac Pro (Eight Cores @ 2.33GHz)
Mac Pro (Four Cores @ 3.00GHz)
Mac Pro (Four Cores @ 2.66GHz)
Stream Add (single-threaded vector)
Mac Pro (Eight Cores @ 2.33GHz)
Mac Pro (Four Cores @ 3.00GHz)
Mac Pro (Four Cores @ 2.66GHz)
Stream Add (multi-threaded vector)
Mac Pro (Eight Cores @ 2.33GHz)
Mac Pro (Four Cores @ 3.00GHz)
Mac Pro (Four Cores @ 2.66GHz)
Stream Triad (single-threaded scalar)
Mac Pro (Eight Cores @ 2.33GHz)
Mac Pro (Four Cores @ 3.00GHz)
Mac Pro (Four Cores @ 2.66GHz)
Stream Triad (multi-threaded scalar)
Mac Pro (Eight Cores @ 2.33GHz)
Mac Pro (Four Cores @ 3.00GHz)
Mac Pro (Four Cores @ 2.66GHz)
Stream Triad (single-threaded vector)
Mac Pro (Eight Cores @ 2.33GHz)
Mac Pro (Four Cores @ 3.00GHz)
Mac Pro (Four Cores @ 2.66GHz)
Stream Triad (multi-threaded vector)
Mac Pro (Eight Cores @ 2.33GHz)
Mac Pro (Four Cores @ 3.00GHz)
Mac Pro (Four Cores @ 2.66GHz)
Conclusion
When it comes to processor-intensive multi-threaded tests, the eight-core Mac Pro is certainly faster than both four-core Mac Pros. However, the eight-core Mac Pro is slower than both four-core Mac Pros when it comes to single-threaded tests, thanks to the fact that its cores run at 2.33GHz (compared to 3.00GHz and 2.66GHz for the four-core Mac Pros). Heck, any processes that uses four threads or less will be faster on the four-core Mac Pros than the eight-core Mac Pro; you’re only going to notice a performance benefit when processes take advantage of the extra cores the eight-core Mac Pro offers.
Should you run out and upgrade your four-core Mac Pro to an eight-core Mac Pro? If you have to ask that question, then probably not. This is the sort of upgrade that appeals to hardware enthusiasts and users that really need more than four processor cores.
Would it make sense for Apple to offer an eight-core Mac Pro? Maybe, if the clock speed of the quad-core processor was comparable to the clock speed of the dual-core processor. Even then, I’m not sure how many users would find the four extra cores worth the extra money.
That doesn’t mean I can’t covet an eight-core Mac Pro, though.
CDRinfo posted some Intel quad-core processor benchmark results earlier this month, including results from Geekbench. While I’ve got concerns about CDRinfo’s benchmark methodology (they under-clocked CPUs to emulate CPUs missing from their lineup, like the E6600 and QX6600), it’s still interesting to see how benchmarks like Geekbench perform on a quad-core CPU.
The folks over at 64-bit-computers.com have published an article comparing the performance of 32-bit and 64-bit Windows Vista, and they’re using Geekbench as their benchmarking tool.
From the article:
Both 32-bit and 64-bit tests were done on a budget AMD Sempron 2800+ powered desktop PC, featuring Asus K8U-X motherboard with 512MB of main memory.
The 32-bit Windows Vista Ultimate achived 99.8 GeekBench points, while the 64-bit version of the same OS gained 110.7 points.
(via Digg)
Our obsession with benchmarks and Geekbench continues! Earlier this year we did a couple of Geekbench Comparisons using a number of different machines. While the comparisons were popular, a number of people thought we were being, well, less than fair since we didn’t have enough high-end CPUs from AMD and Intel.
So, for this Geekbench comparison, I’m including most of the recent AMD and Intel desktop processors (along with some not-so-recent desktop processors) along with a wide variety of recent Mac models, ranging from the PowerBook G4 to the Mac Pro.
This time ’round, instead of using results from a single computer, I’m using average results from all the computers in the Geekbench Result Browser database (provided the results meet certain criteria outlined below). To make sure I’ve got a good sample size for each computer, I’m only including computers (or processors) that have at least three distinct results in the result browser. This should help compensate for differences in components (such as RAM) between different computers.
Setup
For Intel and AMD processors, results were collected from Geekbench for Windows (32-bit) running on systems with processors running at stock speed (i.e., no over-clocked processors) and with at least 512MB of RAM.
For Mac systems, results were collected from Geekbench for Mac OS X (32-bit) running on systems with standard processors (i.e., no over-clocked processors or processor upgrades) and with at least 512MB of RAM.
I’m reporting the average overall score for each processor, where 100 is the score a Power Mac G5 @ 1.6GHz would receive. As always, higher scores are better.
AMD Processors
AMD Athlon 64
AMD Athlon 64 2800+ (Socket 754)
AMD Athlon 64 3000+ (Socket 939)
AMD Athlon 64 3000+ (Socket AM2)
AMD Athlon 64 3200+ (Socket 754)
AMD Athlon 64 3200+ (Socket 939)
AMD Athlon 64 3200+ (Socket AM2)
AMD Athlon 64 3300+ (Socket 754)
AMD Athlon 64 3400+ (Socket 754)
AMD Athlon 64 3400+ (Socket 939)
AMD Athlon 64 3500+ (Socket 939)
AMD Athlon 64 3500+ (Socket AM2)
AMD Athlon 64 3700+ (Socket 754)
AMD Athlon 64 3700+ (Socket 939)
AMD Athlon 64 3800+ (Socket 939)
AMD Athlon 64 3800+ (Socket AM2)
AMD Athlon 64 X2
AMD Athlon 64 X2 3800+ (Socket 939)
AMD Athlon 64 X2 3800+ (Socket AM2)
AMD Athlon 64 X2 4200+ (Socket 939)
AMD Athlon 64 X2 4200+ (Socket AM2)
AMD Athlon 64 X2 4600+ (Socket 939)
AMD Athlon 64 X2 4600+ (Socket AM2)
AMD Athlon 64 X2 4800+ (Socket 939)
AMD Athlon 64 X2 5000+ (Socket AM2)
You can see differences in performance for each processor depending on its socket type (thanks to the type of RAM each socket uses); Socket 754 (which uses single-channel DDR RAM ) is slower than Socket 939 (which uses dual-channel DDR RAM), which in turn is slower than Socket AM2 (which uses dual-channel DDR2 RAM)
You can also see that AMD model numbers are fairly consistent; an AMD Athlon 64 3800+ offers roughly the same performance as an AMD Athlon 64 X2 3800+ (180.2 vs 172.5 for Socket AM2), Unfortunately both are slower than a Pentium 4 3.8GHz (211.0), which suggests the model numbers are somewhat optimistic when compared to Intel CPUs.
Intel Processors
Intel Pentium 4
Intel Pentium 4 2.00GHz (Socket 423)
Intel Pentium 4 2.20GHz (Socket 478)
Intel Pentium 4 2.26GHz (Socket 478)
Intel Pentium 4 2.40GHz (Socket 478)
Intel Pentium 4 2.53GHz (Socket 478)
Intel Pentium 4 2.60GHz (Socket 478)
Intel Pentium 4 2.66GHz (Socket 478)
Intel Pentium 4 2.66GHz (LGA 775)
Intel Pentium 4 2.80GHz (Socket 478)
Intel Pentium 4 2.80GHz (LGA 775)
Intel Pentium 4 2.93GHz (Socket 478)
Intel Pentium 4 2.93GHz (LGA 775)
Intel Pentium 4 3.00GHz (Socket 478)
Intel Pentium 4 3.00GHz (LGA 775)
Intel Pentium 4 3.06GHz (Socket 478)
Intel Pentium 4 3.06GHz (LGA 775)
Intel Pentium 4 3.20GHz (Socket 478)
Intel Pentium 4 3.20GHz (LGA 775)
Intel Pentium 4 3.40GHz (Socket 478)
Intel Pentium 4 3.40GHz (LGA 775)
Intel Pentium 4 3.60GHz (LGA 775)
Intel Pentium 4 3.80GHz (LGA 775)
Intel Pentium D
Intel Pentium D 805 (2.66GHz)
Intel Pentium D 820 (2.80GHz)
Intel Pentium D 830 (3.00GHz)
Intel Pentium D 840 (3.20GHz)
Intel Pentium D 915 (2.80GHz)
Intel Pentium D 920 (2.80GHz)
Intel Pentium D 925 (3.00GHz)
Intel Pentium D 930 (3.00GHz)
Intel Pentium D 940 (3.20GHz)
Intel Pentium D 945 (3.40GHz)
Intel Pentium D 950 (3.40GHz)
Intel Pentium D 955 Extreme Edition (3.46GHz)
Intel Pentium D 965 Extreme Edition (3.73GHz)
Intel Core 2
Intel Core 2 Duo E6300 (1.86GHz)
Intel Core 2 Duo E6400 (2.13GHz)
Intel Core 2 Duo E6600 (2.40GHz)
Intel Core 2 Duo E6700 (2.66GHz)
Intel Core 2 Duo X6800 (2.93GHz)
Looking at these numbers, Pentium D processors don’t seem particularly attractive; on one end, high-end single-core Pentium 4 processors offer better performance, while on the other end dual-core Core 2 chips offer better performance and better power-consumption. I’m not surprised that it’s getting harder and harder to buy Pentium D processors these days (save for the low-end Pentium Ds).
Another interesting thing to note is the jump in performance between the Core 2 Duo E6400 and the Core 2 Duo E6600; moving from 2×1MB to 2×2MB of L2 cache makes a big difference for the Core 2 Duo processor. Speaking of Core 2 Duo processors, the Core 2 Duo X6800 is the fastest dual-core processor in this comparison (with only the dual-processor dual-core Mac Pro @ 3.0GHz being faster overall).
Mac Models
iBook and MacBook
iBook G4 (PowerPC G4 (7450) @ 799MHz x 1)
iBook G4 (PowerPC G4 (7450) @ 933MHz x 1)
iBook G4 (PowerPC G4 (7450) @ 1.0GHz x 1)
iBook G4 (Early 2004) (PowerPC G4 (7450) @ 1066MHz x 1)
iBook G4 (Early 2004) (PowerPC G4 (7450) @ 1199MHz x 1)
iBook G4 (Early 2004) (PowerPC G4 (7450) @ 1.3GHz x 1)
iBook G4 (Mid 2005) (PowerPC G4 (7450) @ 1.3GHz x 1)
iBook G4 (Mid 2005) (PowerPC G4 (7450) @ 1420MHz x 1)
MacBook (Intel Core Duo @ 1.83GHz x 2)
MacBook (Intel Core Duo @ 2.00GHz x 2)
MacBook (Late 2006) (Intel Core 2 Duo @ 2.00GHz x 2)
Mac mini
Mac mini (PowerPC G4 (7450) @ 1.5GHz x 1)
Mac mini (Late 2005) (PowerPC G4 (7450) @ 1.3GHz x 1)
Mac mini (Late 2005) (PowerPC G4 (7450) @ 1.5GHz x 1)
Mac mini (Early 2006) (Intel Core Solo @ 1.50GHz x 1)
Mac mini (Early 2006) (Intel Core Duo @ 1.66GHz x 2)
iMac
iMac (Flat-Panel) (PowerPC G4 (7450) @ 700MHz x 1)
iMac (Flat-Panel) (PowerPC G4 (7450) @ 800MHz x 1)
iMac G4 (17-inch Flat-Panel) (PowerPC G4 (7450) @ 800MHz x 1)
iMac G4 (20-inch Flat-Panel) (PowerPC G4 (7450) @ 1.25GHz x 1)
iMac G5 (PowerPC G5 (970) @ 1.6GHz x 1)
iMac G5 (PowerPC G5 (970) @ 1.8GHz x 1)
iMac G5 (Ambient Light Sensor) (PowerPC G5 (970) @ 1.8GHz x 1)
iMac G5 (Ambient Light Sensor) (PowerPC G5 (970) @ 2.0GHz x 1)
iMac G5 (iSight) (PowerPC G5 (970) @ 1899MHz x 1)
iMac G5 (iSight) (PowerPC G5 (970) @ 2100MHz x 1)
iMac (Early 2006) (Intel Core Duo @ 1.83GHz x 2)
iMac (Early 2006) (Intel Core Duo @ 2.00GHz x 2)
iMac (Late 2006) (Intel Core 2 Duo @ 2.00GHz x 2)
iMac (Late 2006) (Intel Core 2 Duo @ 2.16GHz x 2)
iMac (24-inch) (Intel Core 2 Duo @ 2.16GHz x 2)
iMac (24-inch) (Intel Core 2 Duo @ 2.33GHz x 2)
PowerBook and MacBook Pro
PowerBook G4 (DVI) (PowerPC G4 (7450) @ 800MHz x 1)
PowerBook G4 (1 GHz/867 MHz) (PowerPC G4 (7450) @ 1000MHz x 1)
PowerBook G4 (12-inch) (PowerPC G4 (7450) @ 867MHz x 1)
PowerBook G4 (17-inch) (PowerPC G4 (7450) @ 1.0GHz x 1)
PowerBook G4 (15-inch FW800) (PowerPC G4 (7450) @ 1.25GHz x 1)
PowerBook G4 (12-inch 1.5 GHz) (PowerPC G4 (7450) @ 1.5GHz x 1)
PowerBook G4 (Double-Layer SD, 15-inch) (PowerPC G4 (7450) @ 1.67GHz x 1)
PowerBook G4 (Double-Layer SD, 17-inch) (PowerPC G4 (7450) @ 1.67GHz x 1)
MacBook Pro (Intel Core Duo @ 1.83GHz x 2)
MacBook Pro (Intel Core Duo @ 2.00GHz x 2)
MacBook Pro (Intel Core Duo @ 2.16GHz x 2)
MacBook Pro (17-inch) (Intel Core Duo @ 2.16GHz x 2)
MacBook Pro (Core 2 Duo) (Intel Core 2 Duo @ 2.16GHz x 2)
MacBook Pro (Core 2 Duo) (Intel Core 2 Duo @ 2.33GHz x 2)
MacBook Pro (Core 2 Duo 17-inch) (Intel Core 2 Duo @ 2.33GHz x 2)
Power Mac and Mac Pro
Power Mac G4 (Mirrored Drive Doors) (PowerPC G4 (7450) @ 1.0GHz x 1)
Power Mac G4 (Mirrored Drive Doors) (PowerPC G4 (7450) @ 1.25GHz x 1)
Power Mac G4 (Mirrored Drive Doors) (PowerPC G4 (7450) @ 866MHz x 2)
Power Mac G4 (Mirrored Drive Doors) (PowerPC G4 (7450) @ 1.0GHz x 2)
Power Mac G4 (Mirrored Drive Doors) (PowerPC G4 (7450) @ 1.25GHz x 2)
Power Mac G4 (Mirrored Drive Doors) (PowerPC G4 (7450) @ 1.3GHz x 2)
Power Mac G4 (Mirrored Drive Doors) (PowerPC G4 (7450) @ 1.42GHz x 2)
Power Mac G5 (PowerPC G5 (970) @ 1.6GHz x 1)
Power Mac G5 (PowerPC G5 (970) @ 1.8GHz x 1)
Power Mac G5 (PowerPC G5 (970) @ 1.8GHz x 2)
Power Mac G5 (PowerPC G5 (970) @ 2.0GHz x 2)
Power Mac G5 (June 2004) (PowerPC G5 (970) @ 1.8GHz x 2)
Power Mac G5 (June 2004) (PowerPC G5 (970) @ 2.0GHz x 2)
Power Mac G5 (June 2004) (PowerPC G5 (970) @ 2.3GHz x 2)
Power Mac G5 (June 2004) (PowerPC G5 (970) @ 2.5GHz x 2)
Power Mac G5 (June 2004) (PowerPC G5 (970) @ 2.7GHz x 2)
Power Mac G5 (Late 2005) (PowerPC G5 (970) @ 2.5GHz x 4)
Mac Pro (Intel Xeon @ 2.00GHz x 4)
Mac Pro (Intel Xeon @ 2.66GHz x 4)
Mac Pro (Intel Xeon @ 3.00GHz x 4)
Mac mini performance almost doubled with the switch from a PowerPC G4 @ 1.5GHz to an Intel Core Solo at 1.5GHz with no increase in clock speed. Zomg! iBook and PowerBook (er, MacBook and MacBook Pro) performance also increased dramatically with the switch to the Intel Core Duo (and later to the Intel Core 2 Duo), especially since both went from single-core to dual-core processors.
iMac and PowerMac (er, Mac Pro) performance didn’t benefit as much with the switch to Intel processors since the PowerPC G5 isn’t nearly as old and busted as the PowerPC G4, but the high-end Mac Pro does have a considerable performance advantage over the top-end Power Mac G5. Even the low-end Mac Pro is competitive against the high-end Power Mac G5 (and is substantially cheaper to boot).
Final Thoughts
It’s interesting to see where the bottlenecks in processor and memory performance have occurred over the years (hello, PowerPC G4!) and how processor and computer manufacturers worked around these bottlenecks (hello, Intel!). Really, though, it’s graphs like these that make me want to “accidentally” spill a gallon of water on my three-year-old PowerBook G4 so I can go out and get a shiny new MacBook Pro.
Update: Check out the latest Playstation 3 benchmarks which use Geekbench 2 (the new hotness) instead of Geekbench 2006.
On Sunday I saw a clip of Fedora Core 5 for PPC running on the PlayStation 3 over at Kotaku; I’d completely forgotten that Sony was going to make it easy to boot other operating systems on the PlayStation 3!
On Monday I started receiving requests for Geekbench for Linux PPC so people could run it on the PlayStation 3. I managed to get a beta version out last night and while it’s not quite ready for public release yet, one beta tester sent in the results for his PlayStation 3 which I thought I’d share. To give the results some context, I’m going to compare the PlayStation 3 results against one of the first Power Mac G5s running at 1.6GHz.
Update: Geekbench 2006 for Linux PPC is available now, if you’re interested in benchmarking your PlayStation 3 (or PPC-based Linux box) yourself.
Setup
Playstation 3
- Cell Broadband Engine @ 3.2GHz
- 256 MB RAM
- Fedora Core 5
- Geekbench 2006 (Build 243)
Power Mac G5
- PowerPC G5 @ 1.6GHz
- 1280 MB RAM
- Fedora Core 4
- Geekbench 2006 (Build 243)
I’m reporting the baseline score, rather than the raw score, for each test (where 100 is the score a PowerMac G5 1.6GHz running Mac OS X would receive on the same test). As always, higher scores are better.
Results
Overall Score
PlayStation 3
Power Mac G5
Emulate 6502 (single-threaded scalar)
PlayStation 3
Power Mac G5
Emulate 6502 (multi-threaded scalar)
PlayStation 3
Power Mac G5
Blowfish (single-threaded scalar)
PlayStation 3
Power Mac G5
Blowfish (multi-threaded scalar)
PlayStation 3
Power Mac G5
bzip2 Compress (single-threaded scalar)
PlayStation 3
Power Mac G5
bzip2 Compress (multi-threaded scalar)
PlayStation 3
Power Mac G5
bzip2 Decompress (single-threaded scalar)
PlayStation 3
Power Mac G5
bzip2 Decompress (multi-threaded scalar)
PlayStation 3
Power Mac G5
Floating Point Performance
Mandelbrot (single-threaded scalar)
PlayStation 3
Power Mac G5
Mandelbrot (multi-threaded scalar)
PlayStation 3
Power Mac G5
Dot Product (single-threaded scalar)
PlayStation 3
Power Mac G5
Dot Product (multi-threaded scalar)
PlayStation 3
Power Mac G5
JPEG Compress (single-threaded scalar)
PlayStation 3
Power Mac G5
JPEG Compress (multi-threaded scalar)
PlayStation 3
Power Mac G5
JPEG Decompress (single-threaded scalar)
PlayStation 3
Power Mac G5
JPEG Decompress (multi-threaded scalar)
PlayStation 3
Power Mac G5
Read Sequential (single-threaded scalar)
PlayStation 3
Power Mac G5
Read Sequential (multi-threaded scalar)
PlayStation 3
Power Mac G5
Write Sequential (single-threaded scalar)
PlayStation 3
Power Mac G5
Write Sequential (multi-threaded scalar)
PlayStation 3
Power Mac G5
Stdlib Allocate (single-threaded scalar)
PlayStation 3
Power Mac G5
Stdlib Allocate (multi-threaded scalar)
PlayStation 3
Power Mac G5
Stdlib Write (single-threaded scalar)
PlayStation 3
Power Mac G5
Stdlib Write (multi-threaded scalar)
PlayStation 3
Power Mac G5
Stdlib Copy (single-threaded scalar)
PlayStation 3
Power Mac G5
Stdlib Copy (multi-threaded scalar)
PlayStation 3
Power Mac G5
Stream Copy (single-threaded scalar)
PlayStation 3
Power Mac G5
Stream Copy (multi-threaded scalar)
PlayStation 3
Power Mac G5
Stream Scale (single-threaded scalar)
PlayStation 3
Power Mac G5
Stream Scale (multi-threaded scalar)
PlayStation 3
Power Mac G5
Stream Add (single-threaded scalar)
PlayStation 3
Power Mac G5
Stream Add (multi-threaded scalar)
PlayStation 3
Power Mac G5
Stream Triad (single-threaded scalar)
PlayStation 3
Power Mac G5
Stream Triad (multi-threaded scalar)
PlayStation 3
Power Mac G5
Conclusion
There was a comment on Slashdot last year that made the following assertion about the Cell processor:
The problem is that though the main CPU is PowerPC-based like current Apple chips, it is stripped down, and the Altivec support will be much lower than in current G5s. Unoptomized, Apple code would run like a G4 on this hardware.
Turns out the comment was right; Cell processor performance is comparable to low-end PowerPC G5 performance (which in turn is comparable to high-end PowerPC G4 performance). I can’t comment on Altivec performance, unfortunately, since Geekbench for Linux PPC doesn’t measure Altivec performance yet.
Geekbench also isn’t able to exploit the eight vector processors on the Cell processor. Any program designed and optimized for the Cell processor should be a lot faster than one designed for a generic processor (like, say, Geekbench). So while the Geekbench results might seem disappointing, keep in mind that Geekbench can’t exercise the PlayStation 3 to its full potential.
Apple released updated MacBooks on Wednesday; among the improvements is an upgrade from the Core Duo processor to the Core 2 Duo processor. I thought I’d take a look at the performance of the new Core 2 Duo MacBooks with Geekbench.
Setup
Here’s the setup of the two test machines:
MacBook (Late 2006)
- Intel Core 2 Duo @ 2.0GHz
- 1024 MB RAM
- Mac OS X 10.4.8 (Build 8N1106)
- Geekbench 2006 (Build 230)
MacBook
- Intel Core Duo @ 2.0GHz
- 1024 MB RAM
- Mac OS X 10.4.8 (Build 8L2127)
- Geekbench 2006 (Build 230)
I’m reporting the baseline score, rather than the raw score, for each test (where 100 is the score a PowerMac G5 1.6GHz would receive on the same test). Oh, and for the baseline scores, higher is better. I’m also reporting the results for the 32-bit and 64-bit version of Geekbench for the Core 2 Duo since it’s capable of running both.
Overall Score
MacBook Core 2 Duo (64-bit)
MacBook Core 2 Duo (32-bit)
MacBook Core Duo (32-bit)
Integer Performance
Emulate 6502 (single-threaded scalar)
MacBook Core 2 Duo (64-bit)
MacBook Core 2 Duo (32-bit)
MacBook Core Duo (32-bit)
Emulate 6502 (multi-threaded scalar)
MacBook Core 2 Duo (64-bit)
MacBook Core 2 Duo (32-bit)
MacBook Core Duo (32-bit)
Blowfish (single-threaded scalar)
MacBook Core 2 Duo (64-bit)
MacBook Core 2 Duo (32-bit)
MacBook Core Duo (32-bit)
Blowfish (multi-threaded scalar)
MacBook Core 2 Duo (64-bit)
MacBook Core 2 Duo (32-bit)
MacBook Core Duo (32-bit)
bzip2 Compress (single-threaded scalar)
MacBook Core 2 Duo (64-bit)
MacBook Core 2 Duo (32-bit)
MacBook Core Duo (32-bit)
bzip2 Compress (multi-threaded scalar)
MacBook Core 2 Duo (64-bit)
MacBook Core 2 Duo (32-bit)
MacBook Core Duo (32-bit)
bzip2 Decompress (single-threaded scalar)
MacBook Core 2 Duo (64-bit)
MacBook Core 2 Duo (32-bit)
MacBook Core Duo (32-bit)
bzip2 Decompress (multi-threaded scalar)
MacBook Core 2 Duo (64-bit)
MacBook Core 2 Duo (32-bit)
MacBook Core Duo (32-bit)
Floating Point Performance
Mandelbrot (single-threaded scalar)
MacBook Core 2 Duo (64-bit)
MacBook Core 2 Duo (32-bit)
MacBook Core Duo (32-bit)
Mandelbrot (multi-threaded scalar)
MacBook Core 2 Duo (64-bit)
MacBook Core 2 Duo (32-bit)
MacBook Core Duo (32-bit)
Dot Product (single-threaded scalar)
MacBook Core 2 Duo (64-bit)
MacBook Core 2 Duo (32-bit)
MacBook Core Duo (32-bit)
Dot Product (multi-threaded scalar)
MacBook Core 2 Duo (64-bit)
MacBook Core 2 Duo (32-bit)
MacBook Core Duo (32-bit)
Dot Product (single-threaded vector)
MacBook Core 2 Duo (64-bit)
MacBook Core 2 Duo (32-bit)
MacBook Core Duo (32-bit)
Dot Product (multi-threaded vector)
MacBook Core 2 Duo (64-bit)
MacBook Core 2 Duo (32-bit)
MacBook Core Duo (32-bit)
JPEG Compress (single-threaded scalar)
MacBook Core 2 Duo (64-bit)
MacBook Core 2 Duo (32-bit)
MacBook Core Duo (32-bit)
JPEG Compress (multi-threaded scalar)
MacBook Core 2 Duo (64-bit)
MacBook Core 2 Duo (32-bit)
MacBook Core Duo (32-bit)
JPEG Decompress (single-threaded scalar)
MacBook Core 2 Duo (64-bit)
MacBook Core 2 Duo (32-bit)
MacBook Core Duo (32-bit)
JPEG Decompress (multi-threaded scalar)
MacBook Core 2 Duo (64-bit)
MacBook Core 2 Duo (32-bit)
MacBook Core Duo (32-bit)
Memory Performance
Read Sequential (single-threaded scalar)
MacBook Core 2 Duo (64-bit)
MacBook Core 2 Duo (32-bit)
MacBook Core Duo (32-bit)
Read Sequential (multi-threaded scalar)
MacBook Core 2 Duo (64-bit)
MacBook Core 2 Duo (32-bit)
MacBook Core Duo (32-bit)
Write Sequential (single-threaded scalar)
MacBook Core 2 Duo (64-bit)
MacBook Core 2 Duo (32-bit)
MacBook Core Duo (32-bit)
Write Sequential (multi-threaded scalar)
MacBook Core 2 Duo (64-bit)
MacBook Core 2 Duo (32-bit)
MacBook Core Duo (32-bit)
Stdlib Allocate (single-threaded scalar)
MacBook Core 2 Duo (64-bit)
MacBook Core 2 Duo (32-bit)
MacBook Core Duo (32-bit)
Stdlib Allocate (multi-threaded scalar)
MacBook Core 2 Duo (64-bit)
MacBook Core 2 Duo (32-bit)
MacBook Core Duo (32-bit)
Stdlib Write (single-threaded scalar)
MacBook Core 2 Duo (64-bit)
MacBook Core 2 Duo (32-bit)
MacBook Core Duo (32-bit)
Stdlib Write (multi-threaded scalar)
MacBook Core 2 Duo (64-bit)
MacBook Core 2 Duo (32-bit)
MacBook Core Duo (32-bit)
Stdlib Copy (single-threaded scalar)
MacBook Core 2 Duo (64-bit)
MacBook Core 2 Duo (32-bit)
MacBook Core Duo (32-bit)
Stdlib Copy (multi-threaded scalar)
MacBook Core 2 Duo (64-bit)
MacBook Core 2 Duo (32-bit)
MacBook Core Duo (32-bit)
Stream Performance
Stream Copy (single-threaded scalar)
MacBook Core 2 Duo (64-bit)
MacBook Core 2 Duo (32-bit)
MacBook Core Duo (32-bit)
Stream Copy (multi-threaded scalar)
MacBook Core 2 Duo (64-bit)
MacBook Core 2 Duo (32-bit)
MacBook Core Duo (32-bit)
Stream Copy (single-threaded vector)
MacBook Core 2 Duo (64-bit)
MacBook Core 2 Duo (32-bit)
MacBook Core Duo (32-bit)
Stream Copy (multi-threaded vector)
MacBook Core 2 Duo (64-bit)
MacBook Core 2 Duo (32-bit)
MacBook Core Duo (32-bit)
Stream Scale (single-threaded scalar)
MacBook Core 2 Duo (64-bit)
MacBook Core 2 Duo (32-bit)
MacBook Core Duo (32-bit)
Stream Scale (multi-threaded scalar)
MacBook Core 2 Duo (64-bit)
MacBook Core 2 Duo (32-bit)
MacBook Core Duo (32-bit)
Stream Scale (single-threaded vector)
MacBook Core 2 Duo (64-bit)
MacBook Core 2 Duo (32-bit)
MacBook Core Duo (32-bit)
Stream Scale (multi-threaded vector)
MacBook Core 2 Duo (64-bit)
MacBook Core 2 Duo (32-bit)
MacBook Core Duo (32-bit)
Stream Add (single-threaded scalar)
MacBook Core 2 Duo (64-bit)
MacBook Core 2 Duo (32-bit)
MacBook Core Duo (32-bit)
Stream Add (multi-threaded scalar)
MacBook Core 2 Duo (64-bit)
MacBook Core 2 Duo (32-bit)
MacBook Core Duo (32-bit)
Stream Add (single-threaded vector)
MacBook Core 2 Duo (64-bit)
MacBook Core 2 Duo (32-bit)
MacBook Core Duo (32-bit)
Stream Add (multi-threaded vector)
MacBook Core 2 Duo (64-bit)
MacBook Core 2 Duo (32-bit)
MacBook Core Duo (32-bit)
Stream Triad (single-threaded scalar)
MacBook Core 2 Duo (64-bit)
MacBook Core 2 Duo (32-bit)
MacBook Core Duo (32-bit)
Stream Triad (multi-threaded scalar)
MacBook Core 2 Duo (64-bit)
MacBook Core 2 Duo (32-bit)
MacBook Core Duo (32-bit)
Stream Triad (single-threaded vector)
MacBook Core 2 Duo (64-bit)
MacBook Core 2 Duo (32-bit)
MacBook Core Duo (32-bit)
Stream Triad (multi-threaded vector)
MacBook Core 2 Duo (64-bit)
MacBook Core 2 Duo (32-bit)
MacBook Core Duo (32-bit)
Conclusion
Apple’s claiming up to a 25% performance increase from moving the MacBook from the Core Duo to the Core 2 Duo, and for once, Apple’s claims don’t seem entirely unreasonable; overall performance went up by 18% with the switch to the Core 2 Duo at the same clockspeed, and I’m sure the increase would’ve been larger had we compared the Core Duo @ 1.83GHz against the Core 2 Duo @ 2.0GHz. MacBook 64-bit performance is impressive, too (over 28% faster overall than the Core Duo).
What’s also impressive is the Core 2 Duo MacBook is slightly faster than the Core 2 Duo MacBook Pro I tested a couple of weeks ago, especially when you consider the Core 2 Duo in the MacBook Pro is 160MHz faster. ZOMG!
Overall, when it comes to processor performance, the latest MacBook is an impressive laptop.
On Monday I posted Geekbench results for my Sun Ultra 20 M2 running Solaris and Windows. Afterwards, I received a number of requests asking how Linux performed on the same hardware.
Now that I’ve finally managed to download Fedora Core 6 (arguably the “official” Linux of Geek Patrol), here are the Geekbench results for Fedora Core 6 (and Solaris, as a comparison) on a Sun Ultra 20 M2.
Setup
Here’s the configuration of my Sun Ultra 20 M2:
- AMD Dual-Core Opteron 1210
- 512 MB DDR2-667 RAM (1 DIMM)
- Solaris 10 (6/06)
- Fedora Core 6 (x86_64)
- Geekbench 2006 (Build 230)
I’m reporting the baseline score, rather than the raw score, for each benchmark (where a score of 100 is the score a Power Mac G5 1.6GHz would receive). Higher is better.
Results
Overall Score
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Linux)
Emulate 6502 (single-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Linux)
Emulate 6502 (multi-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Linux)
Blowfish (single-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Linux)
Blowfish (multi-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Linux)
bzip2 Compress (single-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Linux)
bzip2 Compress (multi-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Linux)
bzip2 Decompress (single-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Linux)
bzip2 Decompress (multi-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Linux)
Floating Point Performance
Mandelbrot (single-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Linux)
Mandelbrot (multi-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Linux)
Dot Product (single-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Linux)
Dot Product (multi-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Linux)
JPEG Compress (single-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Linux)
JPEG Compress (multi-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Linux)
JPEG Decompress (single-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Linux)
JPEG Decompress (multi-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Linux)
Read Sequential (single-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Linux)
Read Sequential (multi-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Linux)
Write Sequential (single-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Linux)
Write Sequential (multi-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Linux)
Stdlib Allocate (single-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Linux)
Stdlib Allocate (multi-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Linux)
Stdlib Write (single-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Linux)
Stdlib Write (multi-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Linux)
Stdlib Copy (single-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Linux)
Stdlib Copy (multi-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Linux)
Stream Copy (single-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Linux)
Stream Copy (multi-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Linux)
Stream Scale (single-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Linux)
Stream Scale (multi-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Linux)
Stream Add (single-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Linux)
Stream Add (multi-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Linux)
Stream Triad (single-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Linux)
Stream Triad (multi-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Linux)
Conclusion
Solaris, once again, is faster overall (although only 7.5% faster than Linux, as opposed to 15% faster than Windows); Solaris (and the Sun Studio compiler) is faster in the floating point category while Linux (and GCC) is faster in the stream category.
If you’re using Linux for processor-intensive tasks, it might be worth checking out Solaris (and the Sun Studio compiler) to see if your tasks run faster under Solaris rather than Linux.
Apple updated the MacBook Pro lineup on Tuesday; among other improvements the MacBook Pro now uses the Core 2 Duo processor. I thought I’d take a quick look at the performance of the new MacBook Pros (compared against the “old” MacBook Pros, of course) using Geekbench 2006.
Setup
Here is the setup of the two test machines:
I’m reporting the baseline score, rather than the raw score, for each benchmark (where a score of 100 is the score a Power Mac G5 1.6GHz would receive). I’m also reporting the results for the 32-bit and 64-bit version of Geekbench for the Core 2 Duo (since it’s capable of running both).
As always, higher is better.
Results
Overall Score
Core 2 Duo (64-bit)
Core 2 Duo (32-bit)
Core Duo (32-bit)
Emulate 6502 (single-threaded scalar)
Core 2 Duo (64-bit)
Core 2 Duo (32-bit)
Core Duo (32-bit)
Emulate 6502 (multi-threaded scalar)
Core 2 Duo (64-bit)
Core 2 Duo (32-bit)
Core Duo (32-bit)
Blowfish (single-threaded scalar)
Core 2 Duo (64-bit)
Core 2 Duo (32-bit)
Core Duo (32-bit)
Blowfish (multi-threaded scalar)
Core 2 Duo (64-bit)
Core 2 Duo (32-bit)
Core Duo (32-bit)
bzip2 Compress (single-threaded scalar)
Core 2 Duo (64-bit)
Core 2 Duo (32-bit)
Core Duo (32-bit)
bzip2 Compress (multi-threaded scalar)
Core 2 Duo (64-bit)
Core 2 Duo (32-bit)
Core Duo (32-bit)
bzip2 Decompress (single-threaded scalar)
Core 2 Duo (64-bit)
Core 2 Duo (32-bit)
Core Duo (32-bit)
bzip2 Decompress (multi-threaded scalar)
Core 2 Duo (64-bit)
Core 2 Duo (32-bit)
Core Duo (32-bit)
Floating Point Performance
Mandelbrot (single-threaded scalar)
Core 2 Duo (64-bit)
Core 2 Duo (32-bit)
Core Duo (32-bit)
Mandelbrot (multi-threaded scalar)
Core 2 Duo (64-bit)
Core 2 Duo (32-bit)
Core Duo (32-bit)
Dot Product (single-threaded scalar)
Core 2 Duo (64-bit)
Core 2 Duo (32-bit)
Core Duo (32-bit)
Dot Product (multi-threaded scalar)
Core 2 Duo (64-bit)
Core 2 Duo (32-bit)
Core Duo (32-bit)
Dot Product (single-threaded vector)
Core 2 Duo (64-bit)
Core 2 Duo (32-bit)
Core Duo (32-bit)
Dot Product (multi-threaded vector)
Core 2 Duo (64-bit)
Core 2 Duo (32-bit)
Core Duo (32-bit)
JPEG Compress (single-threaded scalar)
Core 2 Duo (64-bit)
Core 2 Duo (32-bit)
Core Duo (32-bit)
JPEG Compress (multi-threaded scalar)
Core 2 Duo (64-bit)
Core 2 Duo (32-bit)
Core Duo (32-bit)
JPEG Decompress (single-threaded scalar)
Core 2 Duo (64-bit)
Core 2 Duo (32-bit)
Core Duo (32-bit)
JPEG Decompress (multi-threaded scalar)
Core 2 Duo (64-bit)
Core 2 Duo (32-bit)
Core Duo (32-bit)
Read Sequential (single-threaded scalar)
Core 2 Duo (64-bit)
Core 2 Duo (32-bit)
Core Duo (32-bit)
Read Sequential (multi-threaded scalar)
Core 2 Duo (64-bit)
Core 2 Duo (32-bit)
Core Duo (32-bit)
Write Sequential (single-threaded scalar)
Core 2 Duo (64-bit)
Core 2 Duo (32-bit)
Core Duo (32-bit)
Write Sequential (multi-threaded scalar)
Core 2 Duo (64-bit)
Core 2 Duo (32-bit)
Core Duo (32-bit)
Stdlib Allocate (single-threaded scalar)
Core 2 Duo (64-bit)
Core 2 Duo (32-bit)
Core Duo (32-bit)
Stdlib Allocate (multi-threaded scalar)
Core 2 Duo (64-bit)
Core 2 Duo (32-bit)
Core Duo (32-bit)
Stdlib Write (single-threaded scalar)
Core 2 Duo (64-bit)
Core 2 Duo (32-bit)
Core Duo (32-bit)
Stdlib Write (multi-threaded scalar)
Core 2 Duo (64-bit)
Core 2 Duo (32-bit)
Core Duo (32-bit)
Stdlib Copy (single-threaded scalar)
Core 2 Duo (64-bit)
Core 2 Duo (32-bit)
Core Duo (32-bit)
Stdlib Copy (multi-threaded scalar)
Core 2 Duo (64-bit)
Core 2 Duo (32-bit)
Core Duo (32-bit)
Stream Copy (single-threaded scalar)
Core 2 Duo (64-bit)
Core 2 Duo (32-bit)
Core Duo (32-bit)
Stream Copy (multi-threaded scalar)
Core 2 Duo (64-bit)
Core 2 Duo (32-bit)
Core Duo (32-bit)
Stream Copy (single-threaded vector)
Core 2 Duo (64-bit)
Core 2 Duo (32-bit)
Core Duo (32-bit)
Stream Copy (multi-threaded vector)
Core 2 Duo (64-bit)
Core 2 Duo (32-bit)
Core Duo (32-bit)
Stream Scale (single-threaded scalar)
Core 2 Duo (64-bit)
Core 2 Duo (32-bit)
Core Duo (32-bit)
Stream Scale (multi-threaded scalar)
Core 2 Duo (64-bit)
Core 2 Duo (32-bit)
Core Duo (32-bit)
Stream Scale (single-threaded vector)
Core 2 Duo (64-bit)
Core 2 Duo (32-bit)
Core Duo (32-bit)
Stream Scale (multi-threaded vector)
Core 2 Duo (64-bit)
Core 2 Duo (32-bit)
Core Duo (32-bit)
Stream Add (single-threaded scalar)
Core 2 Duo (64-bit)
Core 2 Duo (32-bit)
Core Duo (32-bit)
Stream Add (multi-threaded scalar)
Core 2 Duo (64-bit)
Core 2 Duo (32-bit)
Core Duo (32-bit)
Stream Add (single-threaded vector)
Core 2 Duo (64-bit)
Core 2 Duo (32-bit)
Core Duo (32-bit)
Stream Add (multi-threaded vector)
Core 2 Duo (64-bit)
Core 2 Duo (32-bit)
Core Duo (32-bit)
Stream Triad (single-threaded scalar)
Core 2 Duo (64-bit)
Core 2 Duo (32-bit)
Core Duo (32-bit)
Stream Triad (multi-threaded scalar)
Core 2 Duo (64-bit)
Core 2 Duo (32-bit)
Core Duo (32-bit)
Stream Triad (single-threaded vector)
Core 2 Duo (64-bit)
Core 2 Duo (32-bit)
Core Duo (32-bit)
Stream Triad (multi-threaded vector)
Core 2 Duo (64-bit)
Core 2 Duo (32-bit)
Core Duo (32-bit)
Conclusion
Moving from the Core Duo to the Core 2 Duo means 32-bit MacBook Pro performance is up 10% without an increase in processor clock speed. That’s impressive! Even more impressive is the Core 2 Duo is 20% faster (when executing 64-bit code) than the Core Duo (when executing 32-bit code).
Unless you want to run 64-bit applications (or want one of the other new features the new MacBook Pro offers) I don’t think it makes a lot of sense trade in your old MacBook Pro for a new MacBook Pro. However, coming for almost any other laptop (like, I don’t know, my PowerBook G4), the new MacBook Pro looks like a compelling upgrade, at least from a performance perspective!
I’ve been working with a Sun Ultra 20 M2 workstation, running Solaris 10 and Windows XP, over the past couple of weeks. While I’m going to write up my impressions of the Sun Ultra 20 M2 sometime soon, I thought I’d share some of the performance results I’ve collected on the Ultra 20 M2, especially now that Geekbench runs on Solaris.
Update: Geekbench results for Solaris and Linux running on the same Sun Ultra 20 M2 are now available.
Setup
Here’s the configuration of the Sun Ultra 20 M2:
- AMD Dual-Core Opteron 1210
- 512 MB DDR2-667 (1 DIMM)
- Windows XP Professional x64 Edition or
- Solaris 10 (6/06 Update)
- Geekbench 2006 (build 230)
I’m reporting the baseline score, rather than the raw score, for each benchmark (where a score of 100 is the score a Power Mac G5 1.6GHz would receive). Higher is better.
Overall Score
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Windows XP)
Emulate 6502 (single-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Windows XP)
Emulate 6502 (multi-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Windows XP)
Blowfish (single-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Windows XP)
Blowfish (multi-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Windows XP)
bzip2 Compress (single-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Windows XP)
bzip2 Compress (multi-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Windows XP)
bzip2 Decompress (single-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Windows XP)
bzip2 Decompress (multi-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Windows XP)
Floating Point Performance
Mandelbrot (single-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Windows XP)
Mandelbrot (multi-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Windows XP)
Dot Product (single-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Windows XP)
Dot Product (multi-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Windows XP)
JPEG Compress (single-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Windows XP)
JPEG Compress (multi-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Windows XP)
JPEG Decompress (single-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Windows XP)
JPEG Decompress (multi-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Windows XP)
Read Sequential (single-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Windows XP)
Read Sequential (multi-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Windows XP)
Write Sequential (single-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Windows XP)
Write Sequential (multi-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Windows XP)
Stdlib Allocate (single-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Windows XP)
Stdlib Allocate (multi-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Windows XP)
Stdlib Write (single-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Windows XP)
Stdlib Write (multi-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Windows XP)
Stdlib Copy (single-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Windows XP)
Stdlib Copy (multi-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Windows XP)
Stream Copy (single-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Windows XP)
Stream Copy (multi-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Windows XP)
Stream Scale (single-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Windows XP)
Stream Scale (multi-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Windows XP)
Stream Add (single-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Windows XP)
Stream Add (multi-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Windows XP)
Stream Triad (single-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Windows XP)
Stream Triad (multi-threaded scalar)
Sun Ultra 20 M2 (Solaris)
Sun Ultra 20 M2 (Windows XP)
Conclusion
Overall, I’m pleased with the performance of the Sun Ultra 20 M2. While this model (with an Opteron 1210) isn’t quite as fast as a low-end Mac Pro, it’s less than half the price of a low-end Mac Pro. Models equipped with faster Opterons (like the Opteron 1218) will certainly be more competitive when it comes to performance.
Another thing worth mentioning is that Solaris (and the Sun Studio compiler) outperformed Windows (and Visual C++) by almost 15%. Solaris outperformed Windows in almost every benchmark category, even outperforming Windows dramatically in some specific tests (such as some of the floating point benchmarks). If you’re working with processor-intensive tasks, Solaris might be the operating system for you.