Outlook

Use the turbostat tool to determine whether the energy consumption when playing videos using VA-API is now lower (see the "Consumption Display" box). Table 1 shows the averaged values when playing a video via the mpv media player and for Firefox on a Dell Latitude E7250 with the Broadwell chipset (Intel Core i5 5300U). While mpv obviously benefits from the optimized decoder chip, the savings in Firefox with WebRender are somewhat lower. PowerTOP reports a discharge rate of 7.60W (Figure 3) for VA-API; without it, the system draws 8.56W of power from the notebook battery when playing the video in the browser (Figure 4).

Figure 3: The Firefox web browser can also use hardware acceleration, but support for this function is not yet standard under Linux.

Figure 4: Without VA-API, the system draws nearly 1W more power from the laptop's battery when playing back the video in Firefox's current nightly build.

Thanks to Red Hat's commitment, Firefox on Linux will soon use the graphics card for decoding videos by default, allowing Firefox to finally catch up with the Microsoft Windows 10 version in terms of functionality. Default VA-API integration removes another obstacle to achieving the year of the Linux desktop (if that year ever happens).

As videoconferencing needs increase, encoding videos (of yourself) becomes just as important as decoding the received video data. Many image streams are encoded with VP8, which many graphics cards support. Firefox 80 or 81 can use VA-API for WebRTC [12] after enabling media.ffmpeg.low-latency.enabled in about:config. Hopefully, Firefox will soon enable VA-API integration by default, doing away with all of the manual work.

§§number
$ turbostat --quiet -i 3 -s 'PkgWatt,CorWatt,GFXWatt,RAMWatt'
PkgWatt CorWatt GFXWatt RAMWatt
4.21 1.55 0.13 1.02
4.21 1.55 0.13 1.02
[...]