52
Firefox forks
(sh.itjust.works)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 16 May 2026
52 points (98.1% liked)
Firefox
22761 readers
311 users here now
/c/firefox
A place to discuss the news and latest developments on the open-source browser Firefox.
Rules
1. Adhere to the instance rules
2. Be kind to one another
3. Communicate in a civil manner
Reporting
If you would like to bring an issue to the moderators attention, please use the "Create Report" feature on the offending comment or post and it will be reviewed as time allows.
founded 6 years ago
MODERATORS
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 🤪).