Impressive presentation about whiteboxing WebKit and Chrome by Ilya Grigorik.
I strongly recommend flags that are on slide 21: (Network internals of Chrome) http://www.igvita.com/slides/2012/web-performance-for-the-curious/#21
- chrome://predictors - omnibox predictor stats (tip: check 'Filter zero confidences')
- chrome://net-internals#sockets - current socket pool status
- chrome://net-internals#dns - Chrome's in-memory DNS cache
- chrome://histograms/DNS - histograms of your DNS performance
- chrome://dns - startup prefetch list and subresource host cache
60FPS is not only about games but pages too, so keep an eye on how much code you execute eg. on scroll event.
60FPS affords you a 16.6ms budget per frame
We can use GPU by:
Forcing a GPU layer: -webkit-transform:translateZ(0)
GPU is really fast at compositing, matrix operations and alpha blends
I will suggest to use if mostly by CSS3 animations, or if needed, do not use it for all elements on page.
How to search in chromium like in white box:
Feedback or Comments?
Want to learn more?
Sign up to get a digest of my articles and interesting links via email every month.