Re: wow, that chrome helper sure eats up the cycles

[Dennis Moser <sinsofmachaut@gmail.com>]

Warren, et alia,

It's usually a good idea to turn EVERYTHING that's not involved in the
signal generation or processing OFF on either WIndows or OS X when
you're using a computer for audio. I was shocked to see how much
difference some of the seemingly innocuous things we run for "general"
computing made when left running when trying to use the computer for
any audio-related activities. One of the big culprits is the graphics
card...Airport, FileSharing (there's constant "pinging" going on
there), the list goes on ...

http://soundcloud.com/usrsbin
http://audiozoloft.com
http://usrslashsbin.angrek.com/



On Sun, Aug 22, 2010 at 9:48 AM, Warren Sirota <wsirota@wsdesigns.com> 
wrote:
> I'm running on OSX, and I use Chrome as a browser mostly, although this 
>may
> well apply to Windows too.
> I was wondering why my system, processing-heavy tho it is, seemed to be
> taxing my new computer more than I thought reasonable. So I looked in
> activity monitor - Chrome helper was eating 41% of a cpu! killed it, and
> things are better.
> Note, this was *after* having quit Chrome and shut off Airport!
>
> --
> Warren
> http://www.warrensirota.com
> NEW CD: Loops, Live & Otw
> http://www.cdbaby.com/cd/warrensirota
>