![]() Difference CPU or GPU may very likely produce different results. Note that results can only be compared to other browsers running on the same machine. In closing, I ran various benchmarks on the web. ![]() This is unlike Chromium and Firefox where the Video Engine is not utilized, just GPU. For the first time, I saw the Video Engine (NVIDIA) being used (VP9 media) along with the GPU while watching videos. There are three new sections for Google Chrome, Vivaldi, and Brave. It has a new section “Determine the VAAPI driver to use”. What a journey this has been… and saw the mess the README file has become. Update: Added results for Vivaldi and Brave. As mentioned in a prior post, I’m not able to test against Intel graphics. +-+īoth Chromium and Firefox work well for me. | 0 N/A N/A 982 G /usr/bin/gnome-shell 54MiB | | GPU GI CI PID Type Process name GPU Memory | eatures=VaapiVideoDecoder in the nvidia-smi output. Out-of-process Rasterization: Hardware accelerated.Direct Rendering Display Compositor: Disabled.Canvas out-of-process rasterization: Disabled.Below, Feature Status from the chrome://gpu page. For Chromium, one needs to pass -enable-features=VaapiVideoDecoder flag.
0 Comments
Leave a Reply. |