

This was the purpose of all the other sound daemons (arts, esd, etc) of times past. Indeed, alsa only supports one audio stream.

It is not until one tries to build a native linux app that you see the issue with alsa once you venture into the alsa library docs.

I avoided PA for years because "alsa just works". So I hope the webrender is more stable with Firefox 81, but I think I'll keep Chromium for anything other than watching videos. Note that on Windows10 for the same hardware cpu consumption is between 5% and 10%.įor Chromium and youtube videos cpu consumption it is more like between 20% and 40%. With both vaapi and webrender it is <15% but very unstable. There is this Fishbowl web browser rendering test, for Chromium I can display 100 fish at 60fps, for Firefox (without webrender but hardware acceleration) with 10fish I get only 53fps.įor watching youtube videos (with h264lify on both), I get on firefox between 15%to25% cpu consumption with Vaapi but without webrender. So except for watching videos, the Chromium experience is much smoother and consumes less cpu. Starting from Firefox 79 I had to disable webrender, otherwise youtube videos crashed very frequently. My OS is Archlinux, LTS kernel and my desktop environment is Gnome Wayland. I own a Dell XPS13 9380 with Intel igpu 620 and switched back to Chromium (without the hardware acceleration patch).
