Sujet : Re: OT: Firefox vs Chromium on Fedora 43
De : nospam (at) *nospam* needed.invalid (Paul)
Groupes : comp.unix.programmerDate : 15. Apr 2026, 01:10:56
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <10rml2e$hsi5$1@dont-email.me>
References : 1
User-Agent : THIS SPACE FOR RENT
On Tue, 4/14/2026 3:55 PM, Kalevi Kolttonen wrote:
Hello!
Sorry for the off-topic, but I have to let others
know...
I have been running Firefox as my browser, always.
Today I finally got tired of it being painfully
slow on some sites that I regularly visit.
I tried Chromium and it is so much faster!
Here are the versions that I used
~ $ rpm -qi firefox
Name : firefox
Version : 149.0
Release : 4.fc43
Architecture: x86_64
Name : chromium
Version : 146.0.7680.177
Release : 1.fc43
Architecture: x86_64
br,
KK
https://www.zdnet.com/home-and-office/work-life/i-speed-tested-11-browsers-and-the-fastest-might-surprise-you/ "Start times [lower is better]
Chromium: 1.95 seconds \
Firefox: 1.93 seconds \___ Tests like this need a *lot* of attention to details
Chrome: 0.70 seconds / Clean OS, reboot before test run, and so on.
Speedometer 3.0 results [higher is better]
Firefox: 25.0
Chromium: 30.7
Chrome: 31.5
"
"The margins between the winners and losers here are fairly small. <===
The only reason you might switch to the fastest all-around browser (Chrome)
is if you regularly visit websites that demand speed in ways that require
switching browsers. Or maybe you're a power user who simply wants to ensure
you're using the absolute fastest browser on the market. In that case,
the choice is easy… Chrome. "
And that tells you, there is likely some configuration problem which could
be improved upon. Just an auto-proxy versus no-proxy setting could
do it. Go through the Preferences and make sure they're set the best
way possible. Then the difference between them will be smaller.
The cache on browsers, can be set to disk or set to memory. See
if both browsers are configured the same way. I like memory caching,
just to reduce wear on the SSD. If your cache2 has never been cleaned
and you set the cache size too large inadvertently, that can cause
a big problem. My brother phoned me once about browser speed, and
we decided the root cause was the humongous cache setting he was using.
There might have been something like 300,000 files in the cache at the time,
cached to a hard drive.
Paul
Haut de la page
Les messages affichés proviennent d'usenet.
NewsPortal