On 08/05/2019 07:37, A. Dumas wrote:
> druck wrote, on 07-05-2019 21:22:
>> Excessive CPU and especially memory usage, is the reason Chromium is
>> now the default browser on the Pi. I'd swapped for the same reasons
>> quite a while before.
>
> Well, I'm not sure how much of that is inherently slower Firefox than
> Chromium. My guess is not much; point is mainly, I think, that the
> foundation spent time & effort optimising Chromium for Raspberry Pi
> (after they switched from Epiphany) and no such effort has gone into
> Firefox. Where optimising probably means hooking into proprietary GPU APIs.

The GPU acceleration is only a small factor, the speed of the javascript
engine counts for far more. The biggest issue with any browser and the
Raspberry Pi is limited amount memory, with the maximum on the 2/3/3+
being 1GB (far less than high or mid range mobile phones these days).
Highly optimised javascript and rendering engines tend to use a lot of
memory, so even if FF was inherently faster, if it uses to much too
memory its performance will suffer badly on the Pi.

Chromium's memory management, both how much it uses initially, and how
much it manages to free after closing pages, is quite a bit better than
Firefox. So it performs better on the the Pi, and even more so after a
long browsing session. Although I'd still recommend restarting the
browser regularly to free up memory, and don't keep tabs open you aren't
using.

---druck

--- SoupGate-Win32 v1.05