While it’s not a major departure from the old design, the new design is much cleaner and fits in with the other Primate Labs websites. Also, the new design lays some important groundwork for some new features and functionality I’m hoping to release later this year.
Earlier this month Apple announced a lot of new hardware. While not all of it is available yet (in particular the Core i5 and Core i7 iMacs) most of it is and folks have been asking about how the new hardware performs compared to the old hardware. So, I’ve gathered Geekbench results for the new Mac models and compared them with results for the older Mac models (all results were gathered from the Geekbench Result Browser).
Geekbench is Primate Labs’ processor and memory benchmark where a score of 1000 means a system has the same performance as a PowerMac G5 @ 1.6GHz. Higher scores are better.
Mac mini (Late 2009) Intel Core 2 Duo P8700 2.53 GHz (2 cores)
3563
Mac mini (Early/Late 2009) Intel Core 2 Duo P8400 2.26 GHz (2 cores)
3056
Mac mini (Early 2009) Intel Core 2 Duo P7350 2.0 GHz (2 cores)
2783
Mac mini (Mid 2007) Intel Core 2 T7200 2.0 GHz (2 cores)
2617
Mac mini (Mid 2007) Intel Core 2 T5600 1.83 GHz (2 cores)
2400
Conclusions
The results are as expected; faster processors (of the same architecture) mean higher Geekbench scores. This shouldn’t be surprising since Geekbench is predominantly a CPU benchmark. What I’m interested in seeing, though, is how the Core i5 and Core i7 iMacs stack up; not only do they have a new processor architecture they also have double the number of cores. I wonder if the high-end iMac i7 will (finally!) be comparable to a low-end Mac Pro?
I’ve switched the comment system on the Primate Labs Blog from WordPress’ built-in comments to Disqus. Disqus is a hosted comment and discussion service that offers a lot of nice features; you can “log in” and leave comments with your Twitter, Facebook, or OpenID account (you can also sign up for a Disqus account).
Disqus also enables threaded discussions instead of a flat list of comments, making it easier to reply to one person instead of an entire comment thread. Disqus also (optionally) notifies you when someone responds to your comments, making it easier to follow discussions.
I really hope Disqus makes it easier to have meaningful discussions on the Primate Labs Blog. If you’ve got any questions or comments, you can let me know by posting a comment!
While it’s not something I talk about a lot, many of you already know that Primate Labs is not my full-time job. I have a full-time job (as a software developer) during the day and I work on Primate Labs during my evenings and weekends. Although I lose much of my leisure time, my day job gives me access to amazing technology and Primate labs constantly forces me to deal with new challenges. It is a “double life” that has made me a better developer.
You might wonder why any of this matters to you, my users. I have been fortunate that the companies that I have worked for in the past, including most recently RapidMind, have been willing to allow me to pursue Primate Labs projects. A few weeks ago RapidMind was acquired by Intel. This acquisition has forced me to question what I should do as the developer of a vendor-neutral cross-platform processor benchmark AND as an employee of the world’s largest semiconductor company. Can I remain neutral when it comes to my Geekbench work?
I have considered many options, including selling or open-sourcing Geekbench. Abandoning Geekbench was not an option since Geekbench has over 10,000 registered users, over 170,000 results submitted to the Geekbench Result Browser, and companies all over the world in different industries use Geekbench.
I have decided to continue to work on Geekbench. I will strive to provide a benchmark that remains vendor-neutral in spite of my daytime employment. It is just another challenge, but one that you as Geekbench users should be aware of and understand.
If you have any questions, comments or concerns about this please let me know. You can reach me via email at email hidden; JavaScript is required or by posting a comment below.
I’ve added a page to the Primate Labs website that lists the experimental builds (along with the official releases) of Geekbench. These experimental builds are, well, experimental (meaning things can and probably will break) and come with absolutely no support.
Right now there are experimental builds of Geekbench 2.1 for Solaris and Haiku available on the download page. I’ll update the blog whenever additional builds are available.
Snow Leopard is out today! While I’ve been running the developer versions for a while now, I went out and picked up a retail copy at my friendly neighborhood Apple store and installed it on my MacBook Pro (the laptop where I do most of my Mac development).
Now, what’s interesting about Snow Leopard is that unlike most new versions of operating systems (or most new versions of software in general) Apple didn’t add a lot of new features to Snow Leopard. Instead, Apple focused on making Snow Leopard faster and more stable than Leopard.
While some of the improvements, like Grand Central Dispatch and OpenCL, will only benefit new (or rewritten) applications, do the other improvements help existing applications run faster?
To find out just how much faster existing applications run under Snow Leopard, I ran Geekbench on my MacBook Pro under Leopard and Snow Leopard. Geekbench doesn’t take advantage of Grand Central Dispatch or OpenCL so it’s a good way to determine how much of a performance boost existing applications will receive under Snow Leopard.
Setup
Here’s the configuration of the MacBook Pro I used:
MacBook Pro (Late 2008)
Intel Core 2 Duo P8600 @ 2.40GHz
2.00 GB 1067 MHz DDR3
Mac OS X 10.5.8 or
Mac OS X 10.6
If you’re not familiar with Geekbench, higher scores are better.
Results
Overall Performance
Snow Leopard 64-bit
3725
Leopard 64-bit
3637
Snow Leopard 32-bit
3410
Leopard 32-bit
3310
Integer Performance
Snow Leopard 64-bit
3357
Leopard 64-bit
3230
Snow Leopard 32-bit
2768
Leopard 32-bit
2677
Floating Point Performance
Snow Leopard 64-bit
5199
Leopard 64-bit
5099
Snow Leopard 32-bit
4950
Leopard 32-bit
4773
Memory Performance
Snow Leopard 64-bit
2681
Leopard 64-bit
2630
Snow Leopard 32-bit
2594
Leopard 32-bit
2568
Stream Performance
Snow Leopard 64-bit
1943
Leopard 64-bit
1960
Snow Leopard 32-bit
1907
Leopard 32-bit
1893
Conclusions
While the performance improvement is small, it is there — Geekbench runs between 2% and 3% faster under Snow Leopard than under Leopard. While this might not seem impressive at first keep in mind that Geekbench was slower under Leopard than Tiger. Having a new operating system improve performance, even if it’s a small improvement, is still something to get excited about.
One thing worth mentioning that isn’t captured in the Geekbench results above is that Snow Leopard feels faster and smoother than Leopard; the increased responsiveness of Snow Leopard makes it a joy to use.
I’ve updated the Mac Benchmark chart with Geekbench results for the new MacBook Pros announced at WWDC earlier this month. I’ve included the results for these new MacBook Pros below, along with results for the previous generation of MacBooks and MacBook Pros.
Results were collected from the Geekbench Result Browser for Macs with standard processors (i.e., no processor upgrades or overclocked processors). I’ve reported the average overall score for each model and processor combination. A score of 1000 is the score a Power Mac G5 @ 1.6GHz would receive, and higher scores are better.
Results
MacBook Pro (15/17-inch Mid 2009) Intel Core 2 Duo T9900 3.06 GHz (2 cores)
3989
MacBook Pro (Late 2008) Intel Core 2 Duo T9800 2.93 GHz (2 cores)
3888
MacBook Pro (17-inch Early 2009) Intel Core 2 Duo T9800 2.93 GHz (2 cores)
3872
MacBook Pro (15/17-inch Mid 2009) Intel Core 2 Duo T9600 2.8 GHz (2 cores)
3764
MacBook Pro (Late 2008) Intel Core 2 Duo T9600 2.8 GHz (2 cores)
3652
MacBook Pro (15/17-inch Mid 2009) Intel Core 2 Duo P8800 2.66 GHz (2 cores)
3580
MacBook Pro (Late 2008) Intel Core 2 Duo T9550 2.66 GHz (2 cores)
3548
MacBook Pro (15-inch Mid 2009) Intel Core 2 Duo P8700 2.53 GHz (2 cores)
3437
MacBook Pro (13-inch Mid 2009) Intel Core 2 Duo P8700 2.53 GHz (2 cores)
3436
MacBook Pro (17-inch Early 2009) Intel Core 2 Duo T9550 2.66 GHz (2 cores)
3405
MacBook Pro (Late 2008) Intel Core 2 Duo T9400 2.53 GHz (2 cores)
3293
MacBook Pro (13-inch Mid 2009) Intel Core 2 Duo P7550 2.26 GHz (2 cores)
A few years ago I bought a 15″ PowerBook with an illuminated keyboard. At the time, I didn’t think much of the keyboard:
The keyboard backlight is an interesting idea, and looks very cool, but I’m not sure how practical it is. It’s only really visible when in a pitch-black room, and I can’t remember the last time I used a laptop in a room that dark (save when I was testing the keyboard backlight).
A few days ago, I bought a 15″ MacBook Pro with an illuminated keyboard and unlike the first time around I can’t say how much I’ve missed, and how much I appreciate, having a backlit keyboard.
You see, in between the PowerBook and the MacBook Pro I had a MacBook with a regular keyboard. That keyboard was hard enough to read in dim lighting, let alone complete darkness. Now, though, I have no problem reading the keys.
If you’re considering between an illuminated and a regular keyboard, might I recommend going with the illuminated keyboard. Even if it doesn’t seem like much at first, you’ll soon come to appreciate it.