OK: currently, chrome 517 GPU is designed for 3D transform.

I accidentally pressed SHIFT + ESC, opened chrome memory management, and saw GPU process, occupying nearly MB of memory!

Then let it go:
1. After the GPU process is completed, the 3D Interaction animation of the English official version disappears and returns to the 2D effect.
2. Close the browser and re-open the regular website. If the GPU process is not started, enable the official English version. The GPU process is automatically started and 3D Interactive Animation is displayed.
Conclusion 1: 3D transform and GPU functions are bound, or when the page defines 3D transform, the GPU process is triggered.

3. Close the browser and use chrome to open the SVG or canvas test page of ie9. The GPU process is not triggered.
Conclusion 2: currently, chrome GPU does not accelerate SVG or canvas.

In combination, it is the title of this article. Of course, I believe that Chrome GPU will certainly support SVG or canvas, but compared with Microsoft, Google chose to accelerate css3 first. Google's head is as clear as mine. SVG and canvas are far behind css3 in terms of wide application. I don't think it's a technical maturity issue, but if SVG and canvas are introduced to the front-end now, it will be a revolution, which will bring about great changes to the entire team's collaboration process, let alone the scarcity of talents. Unlike css3, It is a seamless transition and very simple. The transformation brought about by collaboration is also a seamless and progressive improvement.

For example, some time ago, when the front-end of yinglaiwang was struggling with interactive animation design, I realized that in the future there will certainly be such a brand new interface design: interface Design between front-end development engineers and animation designers. This is a new separation and handshaking at the front end, and where should the animation be put? Now I think this problem has vanished. Of course, from my personal thoughts, this is not because of GPU acceleration, but because the positions of development engineers and animation designers are separated, and animation design is more reliant on graphic design, in addition, designing a good animation is very complicated and complicated. It requires not only precise control of pixels, but also time and rhythm, but also audio processing. Therefore, interactive animations with the advent of css3 have always been used for mixing on the web, it will become interaction + Interface + animation. However, there is no room for debate about the emergence of GPUs. Haha, I am thinking about it. I will hire a css3 animation designer ...... But is there any?

From this point of view, ie9 does not yet support transform and transition, but supports SVG and canvas perfectly. As soon as they stood up, they wanted to fly, but developers did not even learn how to run, and even a lot of walks were swinging. Google and me, that's the same brilliant ^ o ^

The chrome GPU performance is still very good. It processes the complex effects of our complex structures and complex environments very smoothly, and even the 3D effect is smoother than the previous 2D effect, it is really not a flickering ornament, but it plays a role. However, there are still many bugs. The most serious problem is that some of the position: Fixed positioning flashes and even disappears completely. There are several amazing phenomena that occur after GPU startup. It should be a GPU rendering bug. I don't need to design the GPU compatibility. How can this problem be solved ~~~

The last one is about the terrible memory consumption of the chrome GPU process, but in special cases, I guess it is related to our own design issues.

Well, the English official version of the release of online there is still a period of time, interested can go to the official WebKit 3D animation demo address: http://webkit.org/blog-files/3d-transforms/morphing-cubes.html

I wanted to lose my post to the blog homepage, but I can't help it. I'm a ninja.