Performance com Interações no DOM

Transcript

1. Performance de Interações no DOM
2. Introduction ! • JavaScript interactions have a "scripting" timing; • That pure JS versus "Write less" jQuery; • JavaScript layouting; • GPU vs CPU; • CSS layout, paint and composite layer in animations; • For each ~16ms we have 1 frame and 60 in 1 second;
3. JavaScript and jQuery Scripting Time window.pageYOffset vs. $(window).scrollTop() more than 100 times faster ! window.innerHeight vs. $(window).height() more than 220 times faster ! el.clientWidth vs. $el.width() more than 50 times faster Tested at! http://jsperf.com
4. JavaScript Layouting Everytime we need to do things like this:! ! el.clientHeight; el.clientWidth; el.offsetTop; ! We force the browser to re-calculate the layout, so if we do:! ! $el.height(); $el.width(); $el.offset().top; ! We have less performance :(
5. CPU vs. GPU https://www.youtube.com/watch?v=-P28LKWTzrI
6. How we use the GPU We can trigger the GPU using:! ! ! CSS3 transitions! CSS3 3D transforms! Canvas Drawing! WebGL 3D Drawing
7. But... We need to say to the browser that we want to use the GPU on our element in 2D animations cases:! ! ! transform: transale3d(0, 0, 0); ! or ! .accelerated { transform: transale3d(0, 0, 0); }
8. ... it is a hack :( but the strongest and best way to do that yet.! ! ! transform: transale3d(0, 0, 0); ! or ! .accelerated { transform: transale3d(0, 0, 0); }
9. The (future) salvation: will-change The will-change property still is an experimental technology and its compatibility is limited.! It tells what will gone change for the browser be able to do specific optmizations for CSS Properties.! ! .el { will-change: transform; } ! ! Browser support! Chrome 36+! Firefox 36+! Opera 24+! Safari (not supported)! Internet Explorer (not supported)
10. Saving your battery Using the GPU we expend much more battery than using our conventional CPU, so the browser doesn't enable it by default for 2D animations. !
11. Saving your battery For that reason you should take care enabling it all the time too. Enabling many times at the same element can make all performance transition be worst.! !
12. Composite vs. Layout vs. Paint
13. Talking about frames ~60Hz! (1 second / 60fps = ~16ms)! ! ! Best animations practices is try to keep the frames in 60fps! and the best way is working with the GPU.! ! And ok, but how to double check it?!
14. Timeline DevTool
15. Timeline DevTool
16. Good to know ! • Layout doesn't work with float numbers;! ! • Painting is fast, but still use only the CPU! ! • The composite layers are transfered to the GPU like bitmaps, combined and then drawn on the screen! • The "layer" is an independent subtree of the DOM, composited at the GPU and possible to move, stretch and fade without repainting!
17. Sources https://www.urbaninsight.com/2013/01/04/improving-html5-app-performance-gpu-accelerated- css-transitions ! http://www.nvidia.com/object/what-is-gpu-computing.html ! https://www.youtube.com/watch?v=-P28LKWTzrI ! http://www.html5rocks.com/en/tutorials/speed/high-performance-animations/ ! https://developer.chrome.com/devtools/docs/timeline ! http://jsfiddle.net/ginpei/GdgYm/ ! http://csstriggers.com/