How to configure the hardware acceleration of Google Chrome on Ubuntu.
I took note of the method for setting hardware acceleration (GPU) in Google Chrome. It's no secret that in most applications in Ubuntu hardware acceleration must be included directly in the application itself. These functions are disabled by default in applications, apparently because hardware acceleration may not be configured in the system itself and this can lead to the failure of the application itself. How to configure DRI (Direct Renderig Infrastructure) in the operating system Ubuntu for the intel driver, I described in a note "How to configure drivers for Intel HD Graphics in Ubuntu 14.04". For other video cards, the driver settings are slightly different. For Nvidia and Amd video cards, you need to download and install proprietary drivers. Methods for their customization are exhaustively described in the articles. Search the Internet for the Internet. Based on the fact that DRI is already set up for me, I decided to check if the acceleration in Google Chrome is enabled?
To do this, I typed in the address bar of the browser "chrome://gpu" and saw the following picture.
Almost all functions are configured as software only, hardware acceleration unavailable (configured by software, hardware acceleration is not available). And it's lousy. To correct this situation, open a new tab and type in the address bar "chrome://flags".
And we include the experimental functions "Redefining the list of software rendering" and "support for experimental canvas"functions. You can enable the function "Number of bitmap streams". This will increase the rendering speed of the images and the value of the "Multiple Raster Threads" parameter. will be "Force enabled". I set the maximum number of threads 4. Next, click the "Restart" button. After the chrome is rebooted, check again by going to the "chrome://gpu"tab.
As you can see, the picture is completely different and more joyful. In order to enable Multiple Raster Threads, you need to find the section "Number of bitmap streams in Mac, Windows, Linux, Chrome OS, Android" (tag # num-raster-threads) and specify the number of bitmap streams. I set the number of threads to four.
And, of course, do not forget to enable hardware acceleration in the settings.
Also, you can include a nice new design from Google - "Material Design".
I read Alex's comment about the absence of the flags of Native GpuMemoryBuffers and Rasterization. These flags are included simply:
To enable Rasterization, you need to type chrome: // flags in the address line, find # enable-gpu-rasterization (ctrl + f) and enable it.
Native GpuMemoryBuffers is slightly more complicated. The bottom line is that you need to run the chrome with the flag --enable-native-gpu-memory-buffers. I did it in KDE like this: run kmenuedit (press alt + F2, write kmenuedit in the line), I found a shortcut to the chrome and appended the /usr/bin/google-chrome-stable%U flag to the command --enable-native- Gpu-memory-buffers. The launch shortcuts in other places are edited approximately identically.
In the end, we get such a picture (I turned off Rasterization - it loads the CPU):
As a result of the action, chrome began to work more vividly.
Another interesting thing in the network.