Chrome 56.0.2924.76 (64-bit) Default settings (chrome://gpu): After applying new settings (chrome://flags/#enable-zero-copy): I succesfully could change the Tile Update Mode to Zero-copy. How to change the Native GpuMemoryBuffers? Ref. https://www.wilderssecurity.com/threads/chrome-stable-channel-update.355822/page-41#post-2649243
Please keep in mind that I could be entirely wrong on this answer, but I recall looking that up a few weeks ago and recall seeing some Chromium developers mentioning that being specific for MacOS only or something like that. I'll have a look later and see if I can dig up the links to those conversations.
Thank you. Hopefully they could add, if not already, support for Windows oses. I mean, I have a pci-e gpu card, not that powerful you might think, as it is a low-end card but enough to take advantage of Chrome's feature.
It was mentioned in some comments on: Chrome’s rendering gets faster: here is what Google does not tell you
Done. Native GpuMemoryBuffers accelerated by hardware in my five Chrome shortcuts + zero-copy. Maybe a placebo effect? Don't know, need further testing/use. But I notice Chrome faster to load webpages.
According to the artice in the following quote, Zero-Copy has a better performance and a better memory consumption. But they have tested it with Intel-Hardware, i'm not sure if the results will be different if "non-Intel" hardware is being used. You can also enable the fps-counter to check the performance: "We measure frames per second (FPS) with the Chrome FPS counter, which can be enabled via --show-fps-counter"
@Mister X You are still missing Rasterization which is most important. I was able to achieve that by using the top flag to disable GPU blacklist.
@mood @WildByDesign Thanks a lot for your support. I wonder when these switches in the shortcuts will become part of chrome://flags/ settings some day. Working on those both last suggestions right away.
There are two options for enable Rasterization: 1. Enabled 2. Force-enabled for all layers Which one to pick...
This the result: Spoiler Looks neat and nice yet it is a bit uncomfortable to have it up there in the corner persistently. I can't move it or hide it at will.
I'm not sure how they exactly tested the performance, and how a user can execute a "performance test suite" On static websites or websites with static content there is no difference (according to google it can be even slower), but on websites with dynamic content there should be a big improvement. But i think you can already "feel" the difference, maybe a benchmark or a performance test is not really needed.
If you go down further on the chrome://gpu/ page, go to the GpuMemoryBuffers Status section There is something like 16 or so different status items under there. Do they still show Software only for you for all of those? Mine are all still showing Software only, despite showing Native GpuMemoryBuffers: Hardware accelerated at the top of the page. I believe that, despite showing accelerated at the top, that GPU memory function is still only functional "under-the-hood" for ChromeOS or MacOS, something like that. But I could certainly be wrong though. Regarding Zero-copy, I do notice a more efficient performing Chromium on most web sites so far. EDIT: As you just mentioned, I "feel" some difference as well which is great.
Also, I wanted to point out I was doing some testing with some of these GPU flags and settings last night. I was able to see with Process Hacker that chrome.exe was utilizing my GPU much more which was nice. On some lesser performing hardware like mine, quite often chrome.exe can become much more CPU intensive. So offloading some of this CPU work onto the GPU for processing has made the overall Chromium experience quite a bit smoother for many rich media on the web. It's good to confirm with Process Hacker that the GPU is, indeed, being utilized which is great as opposed to the GPU just sitting there idle and doing nothing while the CPU takes on much of the work. It's good to see the Chromium development team do more work here with hardware acceleration.
Click on System Information button on top bar of Process Hacker. Click on GPU, then Nodes. You need to select only the nodes which are currently active which you will see some activity on. There could be just one node active or possibly multiple nodes.
Quite often I use YouTube videos (with h264ify extension to push GPU more) and often simple podcasts at the same time in different tabs or windows.
Now i know it. Go to the "test cases" below, there you will found some examples for benchmarking. At the left select the example, paste the code frome the middle into a .html-file and launch the file.
