The first time I saw a Mac Book Pro was at the Apple store, here in Austin about 10 days ago. I gave it a whirl, but after noticing the thing just didn't seem like what I'd call fast, I took a look in /var/vm and noticed there were 6 swapfiles, so the lag was most likely it paging out/in. I checked o see what was running, and after I quit Garage Band, nothing was open but Safari & the Finder. I launched Activity Monitor, and noticed well over 500 MB of RAM 'active.' When I sorted by 'real memory,' the Window Server floated to the top, with 475 MB of RAM. I thought "huh." (I know, I'm a deep thinker, right?) Actually, my first thought as that maybe this is just the way it goes with the Intel hardware, so I went to an Intel iMac across the room & checked it -- no problems, there. The Window Server was soaking about 40 MB of RAM, which is about par for the course, from past experience.
I was back in the store today, and noticed the same thing with two different Mac Book Pros. The Window Server was using upwards of 500 MB of RAM on both, with nothing running but the Finder, and more than 600 MB of RAM listed as 'active.'
Seems like if it was an Intel-wide problem, it'd be happening with the iMacs, too, but no. I doubt it's Rosetta, as there was NOTHING running on any of these machines except for the Finder, and maybe Safari.
Any similar experiences here? I'm curious if it's maybe just a problem with the disk image they use to re-image the machines at the store, or if this is a product-wide symptom.
Top
