lubuntu-desktop team mailing list archive
-
lubuntu-desktop team
-
Mailing list archive
-
Message #05241
Re: [12.04] Firefox instead of Chromium?
Thank you for your test.
I, however, have some doubt about the chromium test.
Since midori, epiphany, and chromium all uses webkit, what makes so many
differences?
The most memory-demanding parts should be webkit and the graphics.
I don't believe that the remaining parts can cause so much impact.
A minimalist webkit browser with few features, midori, uses three times of
memory required by chromium, a complicated and feature-rich webkit browser.
Is that possible? I don't think so, and chromium even loads gtk2 as well.
So the result is really questions. Maybe chromium has some hidden resource
usage not covered by the test?
On Sun, Nov 6, 2011 at 11:16 PM, Jean-Pierre Vidal Piesset <jpxsat@xxxxxxxxx
> wrote:
> Just to get an idea, i've installed and run on my new laptop Epiphany
> 3.0.4, Firefox 7.0.1, Chromium 14.0.835, Midori 0.4.0.
> Here's what i get with two facebook tabs + gmail:
>
> Firefox: 268,7MB ram | 0% CPU
> Epiphany: 261,3MB ram | 0-1% CPU
> Midori: 225,6MB ram | 0-2% CPU
> Chromium: 69+19,8+6,1MB ram (94,9) | 0,0,0% CPU
>
> I'm impress with chromium... maybe there's another process i'm missing?
> (i've only looked at the processes called "chromium-browser")
>
> The faster to open is from far Midori (And the one that has less
> dependencies).
>
> I'll try later those four on my Pentium 3 machine...
>
> @ALI, is there a specific way that you're gonna make your "benchmarks"?
> I'm saying it so we can compare our results :)
>
> --
> JpXsat
>
>
> ______________________________**_________________
> Mailing list: https://launchpad.net/~**lubuntu-desktop<https://launchpad.net/%7Elubuntu-desktop>
> Post to : lubuntu-desktop@lists.**launchpad.net<lubuntu-desktop@xxxxxxxxxxxxxxxxxxx>
> Unsubscribe : https://launchpad.net/~**lubuntu-desktop<https://launchpad.net/%7Elubuntu-desktop>
> More help : https://help.launchpad.net/**ListHelp<https://help.launchpad.net/ListHelp>
>
Follow ups
References