Linked by Thom Holwerda on Sun 3rd Jun 2012 22:04 UTC
Thread beginning with comment 520712
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[10]: Comment by gmlongo
by bhtooefr on Mon 4th Jun 2012 15:29
in reply to "RE[9]: Comment by gmlongo"
If you're using any browser that isn't Chrome, yes, it does impact CPU time.
When I'm on JavaScript heavy sites on my mini-laptop (1.2 Core 2 Duo, FWIW), I can hear the CPU fan ramping up significantly, and the machine gets more sluggish. CPU fan ramping up means it's not a RAM issue (the HDD indicator would be on, for swapping, which I also see often).
RE[11]: Comment by gmlongo
by lucas_maximus on Mon 4th Jun 2012 16:21
in reply to "RE[10]: Comment by gmlongo"
RE[11]: Comment by gmlongo
by lucas_maximus on Mon 4th Jun 2012 16:28
in reply to "RE[10]: Comment by gmlongo"




Member since:
2009-08-18
...says the person who just posted like 5 comments stating that how I use my computer is wrong. Ironic much?
It sounded pretty dumb to me, when whoever designed the UI put in mechanisms that didn't require you to do that so you could get on with other things ... just me
If it is heavy Network activity ... maybe. But if you are talking about CPU time or disk I/O either you have insufficient ram or I am calling bullshit.
I hit 90% CPU time on a compile on my dev box of 90+ C# projects, the compile time is more than several minutes on a Xeon CPU ... and I can browser the web fine on JS/Image heavy sites at the same time.
Edited 2012-06-04 12:25 UTC