Google & Facebook Can Work Together: Timeline Timeline

May 16, 2012 • 8:09 am | comments (0) by twitter Google+ | Filed Under Search Engine Photo Of The Day
 

Facebook & Google

Googler Paul Irish posted a picture on Google+ of Facebook meeting with Googlers at Google for a mini-summit named Timeline Timeline. It was about how Chrome can make Facebook Timelines better.

This is proof Google and Facebook can indeed work together.

The people with the white stick on badges must be the Facebook developers. Here are the names: In the photo (L to R): Nate Chapin, Burak Guzel, Nat Duca, Paul Irish, James Ide, Lior Abraham, James R, (and Steven Young behind the camera).

Here is Paul's notes from the meeting:

  • When figuring out how to speed up the CSS of a site, you need to identify % of time goes to selector matching, style recalculation, reflow and repaint. DevTools Timeline and Speed Tracer can help here.
  • Worried about paint? Toggle off an element’s painting with visibility:hidden and try then.
  • Worried about reflow? Take it out of the render tree with display:none
  • Use requestAnimationFrame to measure FPS
  • You can try out “Threaded compositing” in about:flags for iOS-like scrolling.
  • Fixed background images are very costly to framerate.
  • Chrome lazily decodes images from JPG, etc. Client scaling of images is expensive as it keeps both the original decoded image in memory and the new scale. This can force other images to be evicted from memory which means another re-decoding later on. Chrome Task Manager can watch your image cache numbers: if the image memory consumption is mostly the same while you’re seeing new images, then you’re probably evicting old ones.
  • performance.webkitNow() landed in Chrome and is a big deal: High resolution timing (nanosecond and beyond)
  • A potential way to track memory leaks of DOM nodes is holding element refrences with WeakMaps, run a setTimeout to give some time after “deleting” some DOM and see if the WeakMaps still retain a reference. If so, you probably have a memory leak.
  • It’d be fun to have a contest: You have 1 div and 500 bytes. Make the slowest painting page.

This post is part of our daily Search Photo of the Day column, where we find fun and interesting photos related to the search industry and share them with our readers.

Previous story: Classy: Google Chrome Wrist Watch
 

Comments:

No comments.

blog comments powered by Disqus