Did they? took 2 days… and in the meanwhile I had to manually search the web with CHROME… and to download a sketchy binary from a google drive, where they shared a working deb file of Floorp… so huh.
Oh, well, the fact is that I use Arch btw, so it might have impact on it, maybe. Idk really, because I don’t think that a simply PKGBUILD update would suffice. Maybe just the Debian/Ubuntu artifact was broken?
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 🤪).
What’s performance like? I found it to be very slow the last time I tried it.
I use it daily on my desktop. Works fine. Except yesterday where they published a broken release… Oopsy
Yeah, at least they seemed to repair it fast, though
Did they? took 2 days… and in the meanwhile I had to manually search the web with CHROME… and to download a sketchy binary from a google drive, where they shared a working deb file of Floorp… so huh.
Well, at least for me it has worked within a few hours.
they couldn’t rollback PPA they said… :\
Oh, well, the fact is that I use Arch btw, so it might have impact on it, maybe. Idk really, because I don’t think that a simply PKGBUILD update would suffice. Maybe just the Debian/Ubuntu artifact was broken?
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 🤪).