It may be a matter of hardware compatibility, a bug, or an issue during compilation or installation — I am not entirely sure. However, at least in my case, it runs significantly faster than virtually any other Firefox-based browser, including vanilla Firefox. It reduces CPU and GPU load by approximately 5–10%, which is substantial given my setup: an Intel Xeon v4 (Broadwell-EP, v3 SIMD) clocked at just 2.20 GHz (base, up to 2.90 GHz with Turbo Boost), featuring 12 cores and 24 threads, paired with an NVIDIA GTX 1060 (3 GB VRAM).
Regarding memory consumption, RAM usage does not exceed 4–5 GB, even under a heavy extension load of nearly 100 installed add-ons. That said, this performance might be achieved in part by my custom about:config flags, the use of CachyOS repositories (optimized up to v3), and forced optimized compilation utilizing Mold, LLVM/Clang, Ananicy, and full LTO, among other tweaks, inside of my makepkg.conf (I use Arch, btw 🤪).
It may be a matter of hardware compatibility, a bug, or an issue during compilation or installation — I am not entirely sure. However, at least in my case, it runs significantly faster than virtually any other Firefox-based browser, including vanilla Firefox. It reduces CPU and GPU load by approximately 5–10%, which is substantial given my setup: an Intel Xeon v4 (Broadwell-EP, v3 SIMD) clocked at just 2.20 GHz (base, up to 2.90 GHz with Turbo Boost), featuring 12 cores and 24 threads, paired with an NVIDIA GTX 1060 (3 GB VRAM).
Regarding memory consumption, RAM usage does not exceed 4–5 GB, even under a heavy extension load of nearly 100 installed add-ons. That said, this performance might be achieved in part by my custom
about:configflags, the use of CachyOS repositories (optimized up to v3), and forced optimized compilation utilizing Mold, LLVM/Clang, Ananicy, and full LTO, among other tweaks, inside of my makepkg.conf (I use Arch, btw 🤪).