Browsers in Linux: They own your CPU (and so so in Windows and Mac, too)

I laugh — LAUGH! — when a tech journalist writes something to the effect of, "for lightweight tasks such as Web browsing," when you know, and I know, that there ain't nothing light about using present-day Web browser on present-day Web pages filled with Javascript, Flash and enough CSS to fill a book.

I can edit images all day long in the GIMP and not tap out my CPU or RAM like I do when using Firefox to hit all the Web pages and software-as-a-service type sites (heavy, heavy Javascript) to get my work done.

And this is in Linux, specifically Ubuntu at present. I've run into the same problem in Windows. You start with Firefox or Internet Explorer, and before too long your machine is running like crap.

I spent a bit of time today running most of the browser I have on my Ubuntu 9.04 system, most of which are based on the Gecko engine (Firefox, Epiphany, Galeon), one of which is not (Opera).

And I kept track of how they use CPU resources and memory via the handy Htop utility (top works just as well but isn't nearly as pretty; and you know how I like pretty).

Firefox, no surprise hogs the most CPU on my 1.3 GHz Celeron system (with 1 GB RAM). It's often at 90 percent or more of CPU and rarely dips below 40 or 50 percent. The more pages and the more Javascript and Flash (that's a really killer), the worse it is.

I'm not going to talk so much about memory because with 1 GB, I'm fairly comfortable. With Firefox running, about 400-500 MB is in use; the other browser generally use 200-300 MB.

The other Gecko browsers — the GNOME-supplied Galeon and Epiphany — also spike up to 90 percent when "intensive" things are happening — new pages being loaded, scripts executing, but they quickly "settle" down to 20 percent of CPU and sometimes as little as 10 percent.

Not surprisingly, Opera fared better. The free yet proprietary browser can still use a lot of CPU (in the 90 percent range) during heavy operations. But the difference I see in Opera (I'm running version 10 for Linux and also recommend it for Windows and Macintosh) is that once that instance of heavy use is over, Opera is very quick to give up those CPU cycles and return to a very refreshing 3 to 10 percent of CPU.

However, once the Flash plugin is invoked, all bets are off and Opera is as doggy as anything. It's really Flash that does the damage ... but damage it is. Flash is just plain evil in a box, especially in Linux.

I haven't been as smitten with the Webkit engine, or more specifically the Google Chrome Web browser, as some. In Windows XP with 3 GHz of CPU and 512 MB of RAM, it starts out great but has quite a bit of trouble redrawing the screen in comparison to Firefox once I've been running it for awhile.

I'll certainly keep an eye on Webkit in Linux — Epiphany is supposed to be moving to that engine.

But what I'd like to say once again is that on today's Web, running a browser is quite an intensive operation that requires a whole lot of resources in order to cause as little relative pain as possible to your system — and your nerves.

And there's nothing light about it.

Coming up: One of the 63 dependencies involved in installing digiKam on my GNOME-based, previously KDE-free Ubuntu system is the Konqueror browser. I'll have to try that. And I just added the uber-minimal-GUI-browser Dillo. We'll see how that cuts said mustard.