Apple's MacBook Pro: Using it as a Mac and a PC
by Anand Lal Shimpi on April 13, 2006 12:00 AM EST- Posted in
- Mac
Performance Comparison: G4 vs. Core Duo
Before I get to the actual numbers comparing my PowerBook G4 1.5GHz to the MacBook Pro 2.0GHz, I should say that actually using the machine felt a lot faster. Just scrolling through a Finder window is so much faster on the MacBook Pro than on the old G4. Everything is a lot more responsive and the system as a whole feels desktop-fast. That being said, I can't get away without putting it to the test so here we have it - a PowerMac G4 1.5GHz vs. a MacBook Pro 2.0GHz.
Both systems are configured the way they were from Apple, with 1GB of memory but the original hard drives in each. Obviously the MacBook Pro has an advantage there because of its newer hard drive, however most of my tests aren't very disk bound minimizing the impact of differing hard drives. First off, we've got the good ol' boot test:
The MacBook Pro boots much quicker than the old PowerBook G4, much like the iMac Core Duo boots faster than the iMac G5. While the PowerBook G4 boots (from power on to desktop fully loaded) in just under 50 seconds, the MacBook Pro does it in just over 30 seconds. Although personally I keep my notebook on almost as much as my desktop, boot time is important for traveling where I'm constantly turning my machine on and off.
Just like in my iMac Core Duo review, wherever benchmarks/applications were multi-threaded I tried turning off the second core on the MacBook Pro to give you a good idea of what a Core Solo would be performing like up against the PowerBook G4. Not only is this interesting to look at, but there's also a good possibility that the future iBook replacement will have Core Solo as a processor option. The first two tests here both happen to be multi-threaded so you'll see results from both the Core Solo and Core Duo setups.
The MacBook Pro is ridiculously fast compared to the PowerBook G4 in converting MP3s using iTunes: the encode time is around 35% lower on the MacBook Pro. Disabling one of the cores does significantly level the playing field, although the Core Solo at 2.0GHz still manages to be a bit faster than the G4 1.5.
Under QuickTime we see a full 50% increase in performance over the PowerBook G4. If you disable the second core, the G4 1.5 actually pulls ahead of the Core Solo 2.0. The PowerBook to MacBook Pro upgrade, purely from a performance stance, is looking very impressive already.
52 Comments
View All Comments
nels0360 - Thursday, April 13, 2006 - link
The hardware issue mentioned have been or are being fixed.Apple has release silent revisions of the MacBook Pro. It is well documented on other sites such as Macrumors.com
In fact, I believe Apple will give you a new revision if you complain about one of these problems.
plinden - Thursday, April 13, 2006 - link
I know they are different benchmarks, but over at http://www.macworld.com/2006/04/firstlooks/xpbench...">MacWorld, they found that the MacBook Pro was faster at running Windows than three Windows-only PCs.I'm not going to editorialize here, just bringing this to your attention.
ss284 - Friday, April 14, 2006 - link
Which pretty much drops macworld's benchmark credibility to zero. Actually, their credibility was already really low so its no big deal.ss284 - Friday, April 14, 2006 - link
Unless the benchmark was how fast it could burn a hole in your pants and sterilize your important parts.jbb132 - Thursday, April 13, 2006 - link
Sadly, even the most recent MacBook Pro's continue to suffer from the hardware problems you noticed. I've now had two units with the "whine," particularly when the laptop is running on battery power. The only way to stop it is to turn photobooth on and leave it on. Various hacks (magicnoisekiller in particular) help but really...Pirks - Thursday, April 13, 2006 - link
Hey Anand!Thanks for an interesting review! Now, what was the video source codec and resolution in your H.264 encoding test? I've got a Mac zealot here saying he's got only 2 frames per second in similar H.264 encoding task. He also has Mac OS X 10.4.6 and Quicktime Pro 7.0.4. I wonder is you used source with resolution like 160 by 120 for that test??
To other readers: take with a grain of salt Anand's view on running multiple apps simultaneously in XP. He says something like "uh oh we can't run multiple apps all the time on win coz win can't manage its RAM blah blah", but in fact if you disable XP swap AND if you stick 2 or 3 gigs or RAM in your mobo you'll get my experience of running dozens of apps open at the same time and even some games while at it (DOOM 3 + Matlab + Maya 7 + other little apps like VDub open at the same time is a no brainer on my XP). Stick 4 gigs and open even more, without loss of performance. In fact if you wanna get Mac OS X experience, just stuff your mobo with RAM and turn off swap, that's it, no need to spend $$$ on Mac to get this "experience" :-))
One last minor correction - Anand tells you "anything more than 2GB of RAM on your PC is useless" but he does not know about /3GB switch (google up "/3GB switch") which again allowed me to run Matlab with THREE gigs or RAM consumed, not two.
Just my 2 cents to debunk some myths that Mac zealots love to spread ;) Don't get caught in that stuff, read docs/mans and be smart.
Anand Lal Shimpi - Friday, April 14, 2006 - link
The source for my H.264 test was the Hoodwinked trailer from Apple's Quicktime trailers site.My comments about memory usage and Windows XP have nothing to do with the /3GB switch. The point I was trying to make is that Windows XP does not do a good job of caching to reduce disk accesses. Microsoft itself has admitted that there's lots of room for improvement, which is why you hear about all of the caching improvements that will be introduced in Vista.
Take care,
Anand
kleinwl - Thursday, April 13, 2006 - link
BTW: if you don't think that anandtech knows about the /3GB switch you certainly haven't been here very long.Pirks - Thursday, April 13, 2006 - link
As for the stability - I run Matlab with 3GB consumed routinely, it also loads some Maya 7 stuff internally via my own DLL and there's another Maya 7 hanging around to check results from Matlab quickly, and I never saw a slightest glitch. Of course YMMV but I heard too much "omg windoze is 2GB limited and mac is TrUe 64-bit WoNdEr" and I've got some experience with Matlab on both Mac OS X (no 64-bit matlab there) and WinXP (now this is true 64-bit product) to let Anand repeat that kind of sh.t. Mac guys are ok to say that, they live like this, so no big deal but not Anand please :-) So let's just say "please Anand be a bit more correct in some places and don't sound like a dumb Mac user", saying windows can't properly run a lot of apps at once and stuff like that.
Speaking of Vista I've read somewhere on MSDN that a lot of XP 64 code is in there so it _should_ be as robust as XP 64 with regard to RAM handling. I'm sure after SP1 or SP2 it'll be absolutely rock solid :-) Did Anand ever mention this switch in any of his reviews? Or anyone else besides him from AT staff? I've never seen it before. How about you? Would you provide me with a link or some other proof? I'd love to be corrected here, since AT guys should know about it, and I wish I were wrong stating the opposite, especially about Anand himself.
kleinwl - Thursday, April 13, 2006 - link
I've used the /3GB switch as well... however it can (and does) degrade the stability of your system (running fluent (a CFD program) on XP SP2). I wouldn't run around recommending the normal use of the /3GB switch. Some programs don't even support it (ie. Catia V15). Ultimately we upgraded to XP x64 (which came with it's own headachs).2.5GB seems to be the most that XP SP2 can really handle well.. everything else is a waste. OS X just does a better job handing large amounts of ram and not "losing" it with time.
I am interested is seeing how VISTA will perform and if will be as good as OSX or XP x64 with ram... or something quite better (or worse).