3 ms·

I have Lion, on a 2010 MBP, and I have Activity Monitor open ALL THE TIME. On Snow Leopard, I found what you say to be true. On Lion, either the mysterious pr

by laaph 14y ago

I have Lion, on a 2010 MBP, and I have Activity Monitor open ALL THE TIME. On Snow Leopard, I found what you say to be true. On Lion, either the mysterious process is eluding me, or it is just much slower. I do development and I can tell you that the iPhone Simulator is a frequent culprit, VirtualBox is also rough (but if I ssh in to my virtual machines rather than use the GUI it's fine), also the Time Machine daemon trying to backup causes things to slow down (even when not plugged in to a disk), but even after that performance is downright crap compared to Snow Leopard. If you have any idea what my specific source could be I'd be thrilled to hear it. Frequently at the top of my Activity Monitor is WindowServer and kernel_task, except when compiling or other fun things. Even when the interface is locking up I can't find anything fun.

Zirro 14y ago
Do you by any chance have one or more external hard drives attached? I've been having a lot of lock-up issues while I have six of them connected (through a hub) to a MacBook Pro from 2011 running Lion. It looks like this (also shows it dropping to normal levels instantly): http://cl.ly/1s3N2r2X1u2J2K010H2i http://cl.ly/1s3N2r2X1u2J2K010H2i There's no process running wild from what I can see in the Activity Monitor, but it appears to happen a lot less frequently or not at all when I don't have my external hard drives attached.
- laaph 14y ago
  No external hard drives attached, except when I remember to back up my machine (I frequently, but not always, plug it in when it is on my desk, but it is just for Time Machine). Also, unless I am running heavy CPU things (XCode, VirtualBox machines, etc), I usually don't get a lot of CPU time like that.
  - ZenPsycho 14y ago
    step 1. go into /Library/Quicktime and move ALL the .component files out of there. step 2. Go into ~/Library/Quicktime and move ALL the .component files out of there. step 3. (re)-install perian step 4. Try playing a movie that usually craps out. One of the annoying things about Mac OSX is that a rogue codec can mess up ALL media playing activities on the computer- so when you encounter problems, I've found the most successful strategy is to figure out which codec is messing things up.
batista 14y ago
OK, I don't use VirtualBox, for performance reasons I use VMWare Fusion. Even with this, I find, as you, that using GUI on the VM slows the Mac much more than ssh'ing to the VM. So, the VM is a serious culprit. Certainly, if I have the VM running, I expect some slowdown and occasional swapping -- basically it means I just gave up 1 GB or memory to the VM (out of 2) plus tons of I/O scheduled by a different OS within my OS. Other than that, I also don't run Time Machine at all -- I use Carbon Copy Cloner or Super Duper to make incremental and/or bootable backups every week or so. With iCloud, Dropbox etc for the important day to day documents, I don't see much need for Time Machine anymore. So those would be two places to look at. Besides those, you can try running some DTrace scripts for a more detailed look when your system starts to crap out.
_wwz4 14y ago
The VirtualBox caught my eye... I loved using VirtualBox for a while. It's free. It basically works. It's free. Oh yeah, and it's free. Recently, work sprung for a Parallels license for me. Yikes, I pity my past self for putting up with all the VB issues because it was free. Just little things like playing nicely with the app/spaces switch key combos, lack of crashes, and performance make me really regret wasting all those mental cycles on VB. Don't get me wrong, having a free x86 VM is wonderful and the VB developers deserve kudos galore... but I reminded myself that my time and sanity are worth a few bucks here and there.

by laaph 14y ago

Zirro 14y ago

Do you by any chance have one or more external hard drives attached? I've been having a lot of lock-up issues while I have six of them connected (through a hub) to a MacBook Pro from 2011 running Lion. It looks like this (also shows it dropping to normal levels instantly): http://cl.ly/1s3N2r2X1u2J2K010H2i http://cl.ly/1s3N2r2X1u2J2K010H2i There's no process running wild from what I can see in the Activity Monitor, but it appears to happen a lot less frequently or not at all when I don't have my external hard drives attached.

laaph 14y ago
No external hard drives attached, except when I remember to back up my machine (I frequently, but not always, plug it in when it is on my desk, but it is just for Time Machine). Also, unless I am running heavy CPU things (XCode, VirtualBox machines, etc), I usually don't get a lot of CPU time like that.
- ZenPsycho 14y ago
  step 1. go into /Library/Quicktime and move ALL the .component files out of there. step 2. Go into ~/Library/Quicktime and move ALL the .component files out of there. step 3. (re)-install perian step 4. Try playing a movie that usually craps out. One of the annoying things about Mac OSX is that a rogue codec can mess up ALL media playing activities on the computer- so when you encounter problems, I've found the most successful strategy is to figure out which codec is messing things up.

batista 14y ago

OK, I don't use VirtualBox, for performance reasons I use VMWare Fusion. Even with this, I find, as you, that using GUI on the VM slows the Mac much more than ssh'ing to the VM. So, the VM is a serious culprit. Certainly, if I have the VM running, I expect some slowdown and occasional swapping -- basically it means I just gave up 1 GB or memory to the VM (out of 2) plus tons of I/O scheduled by a different OS within my OS. Other than that, I also don't run Time Machine at all -- I use Carbon Copy Cloner or Super Duper to make incremental and/or bootable backups every week or so. With iCloud, Dropbox etc for the important day to day documents, I don't see much need for Time Machine anymore. So those would be two places to look at. Besides those, you can try running some DTrace scripts for a more detailed look when your system starts to crap out.

_wwz4 14y ago

The VirtualBox caught my eye... I loved using VirtualBox for a while. It's free. It basically works. It's free. Oh yeah, and it's free. Recently, work sprung for a Parallels license for me. Yikes, I pity my past self for putting up with all the VB issues because it was free. Just little things like playing nicely with the app/spaces switch key combos, lack of crashes, and performance make me really regret wasting all those mental cycles on VB. Don't get me wrong, having a free x86 VM is wonderful and the VB developers deserve kudos galore... but I reminded myself that my time and sanity are worth a few bucks here and there.