YouTube home Comedy Week on YouTube
Upload

Google I/O 2012 - Jank Busters: Building Performant Web Apps

GoogleDevelopers GoogleDevelopers·2,071 videos
328,707
15,965
Like     Dislike 3

Sign in to YouTube

Sign in with your Google Account (YouTube, Google+, Gmail, Orkut, Picasa, or Chrome) to like GoogleDevelopers's video.

Sign in to YouTube

Sign in with your Google Account (YouTube, Google+, Gmail, Orkut, Picasa, or Chrome) to dislike GoogleDevelopers's video.

Sign in to YouTube

Sign in with your Google Account (YouTube, Google+, Gmail, Orkut, Picasa, or Chrome) to add GoogleDevelopers's video to your playlist.

Published on Jun 29, 2012

Nat Duca, Tom Wiltzius

Building high-performance web apps is hard! When animations hitch, mouse hover effects lag, or page scrolls stutter, we call it jank. This talk is about hunting jank down and exterminating it.

Sources of jank in web apps include garbage collector runs, long image decodes, heavy paint times for DOM elements, JavaScript-heavy input handlers, unexpected WebKit layer invalidations, and more -- all getting in the way of the 60FPS every modern app developer should aim for. In this talk we'll go through a few techniques to ensure your web app has smooth animations, transitions, and scrolling. We'll cover ways to use Chrome's Developer Tools to root out jank, as well as more advanced Chrome graphics profiling tools the intrepid can use to dig into what's going on behind the scenes. We'll even peek gingerly under the covers of WebKit to explain why that pesky hitch occurs in the first place.

For all I/O 2012 sessions, go to https://developers.google.com/io/

Loading icon Loading...

Loading icon Loading...

Loading icon Loading...

The interactive transcript could not be loaded.

Loading icon Loading...

Loading icon Loading...

Ratings have been disabled for this video.
Rating is available when the video has been rented.
This feature is not available right now. Please try again later.

All Comments (19)

Sign in now to post a comment!
  • Josh Bedo

    Chromium is intended for developers and has a lot of unreleased features because they're still in production but they help developers. Things like convert CSS to SASS and revisioning.

    ·

    Sign in to YouTube

    Sign in with your YouTube Account (YouTube, Google+, Gmail, Orkut, Picasa, or Chrome) to rate Josh Bedo's comment.

    Sign in to YouTube

    Sign in with your YouTube Account (YouTube, Google+, Gmail, Orkut, Picasa, or Chrome) to rate Josh Bedo's comment.
    in reply to Homezone (Show the comment)
  • dsego84

    Maybe chrome is janky, Safari is smooth as butter.

    ·

    Sign in to YouTube

    Sign in with your YouTube Account (YouTube, Google+, Gmail, Orkut, Picasa, or Chrome) to rate dsego84's comment.

    Sign in to YouTube

    Sign in with your YouTube Account (YouTube, Google+, Gmail, Orkut, Picasa, or Chrome) to rate dsego84's comment.
  • Homezone

    They work for Google and use Chromium? o_O

    ·

    Sign in to YouTube

    Sign in with your YouTube Account (YouTube, Google+, Gmail, Orkut, Picasa, or Chrome) to rate Homezone's comment.

    Sign in to YouTube

    Sign in with your YouTube Account (YouTube, Google+, Gmail, Orkut, Picasa, or Chrome) to rate Homezone's comment.
  • ericthewino

    cool. thanks for pointing me to the time. i guess it would be best to recache on resize.

    ·

    Sign in to YouTube

    Sign in with your YouTube Account (YouTube, Google+, Gmail, Orkut, Picasa, or Chrome) to rate ericthewino's comment.

    Sign in to YouTube

    Sign in with your YouTube Account (YouTube, Google+, Gmail, Orkut, Picasa, or Chrome) to rate ericthewino's comment.
    in reply to fezec (Show the comment)
  • fezec

    It's because they already retrieved the layout calculation. Note the code at 13:08. Line 57 says if heavy scroll which is what he toggles on his demo. This forces line 58 to run, which retrieves the scrollTop from the body, forcing a calculation of the DOM, but line 54 shows that he already asked for this.

    When he toggles off heavyScroll rather than use line 58 it uses 60 in the else statement. Here it makes use of the cachedScrollTop thereby not forcing yet another recalculation.

    ·

    Sign in to YouTube

    Sign in with your YouTube Account (YouTube, Google+, Gmail, Orkut, Picasa, or Chrome) to rate fezec's comment.

    Sign in to YouTube

    Sign in with your YouTube Account (YouTube, Google+, Gmail, Orkut, Picasa, or Chrome) to rate fezec's comment.
    in reply to ericthewino (Show the comment)
  • ericthewino

    sorry i don't get what happened around 14:40 that made the event less delay. was the scrolltop cached?

    ·

    Sign in to YouTube

    Sign in with your YouTube Account (YouTube, Google+, Gmail, Orkut, Picasa, or Chrome) to rate ericthewino's comment.

    Sign in to YouTube

    Sign in with your YouTube Account (YouTube, Google+, Gmail, Orkut, Picasa, or Chrome) to rate ericthewino's comment.
  • Lucas Rizoli

    This is a very good talk: your explanations and recommendations and demos are clear, you handle the questions well and frankly. Thanks.

    ·

    Sign in to YouTube

    Sign in with your YouTube Account (YouTube, Google+, Gmail, Orkut, Picasa, or Chrome) to rate Lucas Rizoli's comment.

    Sign in to YouTube

    Sign in with your YouTube Account (YouTube, Google+, Gmail, Orkut, Picasa, or Chrome) to rate Lucas Rizoli's comment.
  • MediaFilter

    Funny guys, good talk!

    ·

    Sign in to YouTube

    Sign in with your YouTube Account (YouTube, Google+, Gmail, Orkut, Picasa, or Chrome) to rate MediaFilter's comment.

    Sign in to YouTube

    Sign in with your YouTube Account (YouTube, Google+, Gmail, Orkut, Picasa, or Chrome) to rate MediaFilter's comment.
  • Loading comment...
Loading...
Loading...
Working...
Sign in to add this to Watch Later