Yes, I have disabled “acceleration” in Firefox, which improves performance but nowhere close to being enough. Websites with even a little bit of JS interactivity in them, not to mention ones showing interactive charts and ability to trade markets, are slow enough to be practically useless.
I’m not dunking on anyone. I understand there are costs to the added security. I just want to understand the reasons.
Is the reason fundamentally the lack of GPU capability in Qubes?
Will this ever get solved? I heard when Wayland becomes ready and replaces X, full GPU capability will be possible on Qubes and Qubes will become just as usable as any other Linux. Is this true?
Are you using the Firefox that comes with the template?
I always get slow performance with it, no matter how many vCPUs I add to the qube. It might be related to the patches they use when they package it. If I use the binary from the official website or the flatpak package, everything works ok, even with 2 vCPUs.
Thanks, this appeared to help a lot. However I also noticed using the Firefox (“Firefox ESR”) from the debian (debian-11 or debian-12-xfce in my case) templates was also a similar improvement. @DVM did you try on debian too?
I wonder why this got messed up on the fedora (fedora-38 or fedora-38-xfce in my case) templates. The slowdown is striking on e.g. video playback in the browser.
Worth repeating: Yes, in all cases did I disable hardware acceleration in the Firefox settings.
I don’t use Firefox ESR from the Debian template, so I can’t say if it’s better. But what I can say is that I never had any problems with the Firefox package coming from Mozilla, they even recently released an apt repo if you want to get the stable Firefox release with the upgrade handled by apt.