The Fastest Linux Distributions For Web Browsing - Firefox + Chrome Benchmarks On Eight Distros

[make_adobe_on_Linux!]

This is such a silly way to pick a distribution. How much faster is one vs another going to be for browsing? Imperceptibly! Best for you just to 1) pick the right browsers 2) learn to optimize your system 3) learn to optimize your browser(s).

I would recommend (in order):
-- pale moon
-- ungoogled-chromium
-- waterfox

In addition to the type of acceleration they discuss in that page I'm talking about hardware video acceleration, ie va-api. Without it playing a H264/HEVC/etc video eats nearly all CPU, causes fans to spin at full speed, etc. Chrome/Chromium still does not support video acceleration under Linux even when checking various experimental boxes in config. It needs a patch that has existed for many years, at least since 2014, but is still not applied. Yet it works just fine under ChromeOS, it seems they have vested interest in not having it work under regular Linux.

The same general situation applies to Firefox as well.

The Firefox bug is here:
https://bugzilla.mozilla.org/show_bug.cgi?id=1210726

I totally agree. In the Adobe flash player plugin era the hardware acceleration worked fine. Then, no more hardware acceleration. Chromium-va-api exeriment tells me it is possible.
If someone can tell me how to use flash player nowaday to watch youtube and others I'll say him "thank you".

[HadrienG]

A good backup startegy is absolutely required if you use btrfs, you -will- need to restore from them sooner rather than later.

All my / partitions have been on btrfs for the last three years, and I have yet to encounter a single data corruption issue. Even big companies like Facebook and Synology feel safe using it in production these days. I think the rumors of btrfs eating data for lunch might be outdated, at least on the simple storage configurations that I use.

[starshipeleven]

It's more like "many and various design flaws". Many of which are hardcoded into the disk layout and can't be fixed.

Why you keep talking trash about things you don't even understand. What the fuck is "disk layout" anyway, it can't be the "on-disk format" as any of your claimed issues would be driver issues.

[calc]

It seems there's a mesa bug blocking the patches as it causes heavy corruption on AMD cards: https://bugs.freedesktop.org/show_bug.cgi?id=106490

Not a particularly good reason to leave the code out altogether instead of just hiding it behind an experimental flag like they do with other things. And could blacklist the AMD cards on top of it like they do for other graphics issues.

[V10lator]

It needs a patch that has existed for many years, at least since 2014, but is still not applied. Yet it works just fine under ChromeOS, it seems they have vested interest in not having it work under regular Linux.

It seems there's a mesa bug blocking the patches as it causes heavy corruption on AMD cards: https://bugs.freedesktop.org/show_bug.cgi?id=106490

[deant]

debian gives eye enojoyable all rounded performance.

[Alliancemd]

I made myself a script to compile Chromium(would compile Firefox but it is harder) from Git with -mtune=native, -march=native, LTO + PGO and it runs significantly(the difference in the startup times is night and day) faster than any browser I could use - Chromium compiles all of its dependencies, so you basically optimize the entire stack, the dependencies + the browser itself.

[calc]

https://www.cnet.com/how-to/3-ways-t...s-performance/

" There is some debate on whether hardware acceleration helps or harmsperformance"

Enabling that option causes troubles often.

In addition to the type of acceleration they discuss in that page I'm talking about hardware video acceleration, ie va-api. Without it playing a H264/HEVC/etc video eats nearly all CPU, causes fans to spin at full speed, etc. Chrome/Chromium still does not support video acceleration under Linux even when checking various experimental boxes in config. It needs a patch that has existed for many years, at least since 2014, but is still not applied. Yet it works just fine under ChromeOS, it seems they have vested interest in not having it work under regular Linux.

The same general situation applies to Firefox as well.

The Firefox bug is here:
https://bugzilla.mozilla.org/show_bug.cgi?id=1210726

[calc]

The Fastest Linux Distributions For Web Browsing - Firefox + Chrome Benchmarks On Eight Distros

The answer is none of them, both the browsers are a bad joke.

They don't have hardware acceleration disabled by a user config option, but at build time. You have to enable the options, and apply patches to get it to work. So even if you use something like --ignore-gpu-blacklist you still won't get video acceleration on Hulu, Netflix, YouTube, etc in 2019.