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

[Warren Sirota <wsirota@wsdesigns.com>]

I think the upshot is that before you play, it's always a good idea to check Activity Monitor (OSX) or Task Manager (Win) to see if there are more processes eating up cpu. You can easily sort these lists on cpu %. That chrome process isn't there for me all the time, but i had in fact quit chrome an hour earlier when i discovered it (so I wasn't trying to check email while playing).

On Mon, Aug 23, 2010 at 3:39 PM, Per Boysen <perboysen@gmail.com> wrote:

Come on, guys - who cares what cycles a web browser eats in 2010!!!
You aren't checking email on stage are you? ;-))

I prefere Chrome for the only reason that it gives me a fast and
convenient edit window in Gmail and in the Wordpress admin system.
Plus that it remembers a set-up of default tabs (if Safari did that I
would rathe use that one, but efficiency is what counts for me)

Greetings from Sweden

Per Boysen
www.boysen.se
www.perboysen.com
www.looproom.com internet music hub

On Mon, Aug 23, 2010 at 7:52 PM, keith mcmillen <keefer07@yahoo.com> wrote:
> I watch this pretty closely and I see Firefox as the worse offender, followed by
> Chrome and then Safari.  (Mac OSX obviously).
>
> The CPU usage will vary with what you have down with the browser. If you view
> videos or have Java applets running and lots of open sites it get's comic. I
> have seen Firefox use 80% on a fast machine.
>
> Turn everything off - it is unfortunate - but it is the only way to get your
> machine back.
>
> Keith
>  Keith McMillen
> www.keithmcmillen.com
> www.beamfoundation.org
> "Music For A New Reason"

>
>
>
> ----- Original Message ----
> From: Dennis Moser <sinsofmachaut@gmail.com>
> To: Loopers-Delight@loopers-delight.com
> Sent: Sun, August 22, 2010 9:09:09 AM
> Subject: Re: wow, that chrome helper sure eats up the cycles
>
> 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
>>
>
>

-- 
Warren
http://www.warrensirota.com
NEW CD: Loops, Live & Otw
http://www.cdbaby.com/cd/warrensirota