High Performance JavaScript (CapitolJS 2011)
Upcoming SlideShare
Loading in...5
×
 

High Performance JavaScript (CapitolJS 2011)

on

  • 13,935 views

 

Statistics

Views

Total Views
13,935
Views on SlideShare
13,419
Embed Views
516

Actions

Likes
59
Downloads
334
Comments
6

24 Embeds 516

http://paper.li 159
http://coderinsights.blogspot.com 158
http://us-w1.rockmelt.com 41
http://ethertank.tumblr.com 35
http://twitter.com 26
https://twitter.com 19
http://coderinsights.blogspot.in 18
http://lanyrd.com 14
http://flavors.me 13
http://a0.twimg.com 6
https://si0.twimg.com 5
http://tweetedtimes.com 4
http://simplypavi.flavors.me 3
http://www.linkedin.com 3
http://feeds.feedburner.com 2
https://www.linkedin.com 2
http://safe.tumblr.com 1
https://twimg0-a.akamaihd.net 1
http://wiki.onakasuita.org 1
http://coderinsights.blogspot.de 1
http://trunk.ly 1
http://coderinsights.blogspot.fr 1
http://translate.googleusercontent.com 1
http://www.onlydoo.com 1
More...

Accessibility

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
  • Thank you, very useful.
    Are you sure you want to
    Your message goes here
    Processing…
  • @HYCLEN No Spam!
    Are you sure you want to
    Your message goes here
    Processing…
  • 11-Bom dia amigos, Venham conhecer nossos Servidores de Mu Online
    O Jogando.net/mu Mu Online Season 6
    Fazemos sua Diversão com qualidade,há mais de 5 anos
    Servers ON 24 horas por dia.
    Vários Server esperando por você.Venha se divertir de verdade.
    Venham participar do 6° Megaultrasuperhiper Evento Castle Siege
    Sejam benvindos ao nosso Servidor.
    >>Kits DIAMOND,Com asas LVL 4,os kits mais fortes e raros do servidor ,venham conferir.
    >>Qual o seu Time ?? Tenha o seu Time do coração no Mu Online.Sets do seu Time preferido
    >>Confiram a nova versão do Shild mais usado no servidor o SHILD POWER v3.
    >> Lançamento do NOVO Kit Fusion V2,Kit hiper top e bonito.
    Você só encontra no http://www.jogando.net/mu/
    Facebook: http://www.facebook.com/profile.php?id=100002113910611
    Site http://www.jogando.net/mu/ HYCLEN Divulgadora Oficial !!!
    Boa Semana á todos !!!
    Are you sure you want to
    Your message goes here
    Processing…
  • Yes, High Performance Javascript
    Are you sure you want to
    Your message goes here
    Processing…
  • ...Excellent....I got a $829.99 iPad2 for only $103.37 and my mom got a $1499.99 HDTV for only $251.92, they are both coming with USPS tomorrow. I would be an idiot to ever pay full retail prices at places like Walmart or Bestbuy. I sold a 37' HDTV to my boss for $600 that I only paid $78.24 for.I use.
    http://xub.me/Lb
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Over the past couple of years, we've seen JavaScript development earn recognition as a true discipline. The idea that you should architect your code, use patterns and good programming practices has really elevated the role of the front end engineer. In my opinion, part of this elevation has been the adoption of what has traditionally been considered back end methodologies. We now focus on performance and algorithms, there's unit testing for JavaScript, and so much more. One of the areas that I've seen a much slower than adoption that I'd like is in the area of error handling.How many people have an error handling strategy for their backend? How many have dashboards that display problems with uptime and performance? How many have anything similar for the front end?Typically, the front end has been this black hole of information. You may get a few customer reports here and there, but you have no information about what's going on, how often it's occurring, or how many people have been affected.
  • So what have we talked about? Maintainable JavaScript is made up of four components.First is Code Conventions that describe the format of the code you’re writing.Second is Loose Coupling – keeping HTML, JavaScript, and CSS on separate layers and keeping application logic out of event handlers.Third is Programming Practices that ensure your code is readable and easily debugged.Fourth is creating a Build Process

High Performance JavaScript (CapitolJS 2011) High Performance JavaScript (CapitolJS 2011) Presentation Transcript

  • High Performance JavaScript
    Nicholas C. Zakas| CapitolJS | September 18, 2011
  • Who's this guy?
    Co-Creator csslint.net
    Contributor,
    Creator of YUI Test
    Ex-tech lead
    Yahoo!
    Author
    Lead Author
    Contributor
    Lead Author
  • @slicknet
    (complaints: @voodootikigod)
  • Does JavaScript performance matter?
  • All browsers now haveoptimizing JavaScript engines
    Tracemonkey/
    JaegarMonkey
    (3.5+)
    V8
    (all)
    Nitro
    (4+)
    Chakra
    (9+)
    Karakan
    (10.5+)
  • http://ie.microsoft.com/testdrive/benchmarks/sunspider/default.html
  • Old computers ran slow applications
    Small amounts of CPU power and memory
  • New computers are generally faster but
    slow applications still exist
    More CPU + more memory = less disciplined application development
  • Oh yeah, one more thing
  • It's still possible to write slow JavaScript
  • JavaScript performancedirectlyaffects user experience
  • The UI Threadaka Browser Event Loop
  • The browser UI thread is responsible for
    both UI updates and JavaScript execution
    Only one can happen at a time
  • Jobs for UI updates and JavaScript execution
    are added to a UI queue
    Each job must wait in line for its turn to execute
  • <button id="btn" style="font-size: 30px; padding: 0.5em 1em">Click Me</button>
    <script type="text/javascript">
    window.onload = function(){
    document.getElementById("btn").onclick = function(){
    //do something
    };
    };
    </script>
  • Before Click
    UI Thread
    time
    UI Queue
  • When Clicked
    UI Thread
    time
    UI Queue
    UI Update
    onclick
    UI Update
  • When Clicked
    UI Thread
    UI Update
    time
    UI Queue
    onclick
    Draw down state
    UI Update
  • When Clicked
    UI Thread
    onclick
    UI Update
    time
    UI Queue
    UI Update
  • When Clicked
    UI Thread
    onclick
    UI Update
    UI Update
    time
    UI Queue
    Draw up state
  • No UI updates while JavaScript is executing
  • JavaScript May Cause UI Update
    <button id="btn" style="font-size: 30px; padding: 0.5em 1em">Click Me</button>
    <script type="text/javascript">
    window.onload = function(){
    document.getElementById("btn").onclick = function(){
    var div = document.createElement(“div”);
    div.className = “tip”;
    div.innerHTML = “You clicked me!”;
    document.body.appendChild(div);
    };
    };
    </script>
  • A UI update must use the latest info available
  • Long-running JavaScript=Unresponsive UI
  • Responsive UI
    UI Thread
    JavaScript
    UI Update
    UI Update
    time
  • Unresponsive UI
    UI Thread
    JavaScript
    UI Update
    UI Update
    time
  • The longer JavaScript runs,the worse the user experience
  • The runaway script timer prevents JavaScript
    from running for too long
    Each browser imposes its own limit (except Opera)
  • Internet Explorer
  • Firefox
  • Safari
  • Chrome
  • Runaway Script Timer Limits
    Internet Explorer: 5 million statements
    Firefox: 10 seconds
    Safari: 5 seconds
    Chrome: Unknown, hooks into normal crash control mechanism
    Opera: none
  • How Long Is Too Long?
    “0.1 second [100ms] is about the limit for having the user feel that the system is reacting instantaneously, meaning that no special feedback is necessary except to display the result.”
    - Jakob Nielsen
  • Translation:No single JavaScript job should execute for more than 100ms to ensure a responsive UI
  • Recommendation:Limit JavaScript execution to no more than 50msmeasured on IE6 :)
  • Loadtime TechniquesDon't let JavaScript interfere with page load performance
  • During page load, JavaScript takes more time on the UI thread
  • <!doctype html>
    <html>
    <head>
    <title>Example</title>
    </head>
    <body>
    <p>Hello world!</p>
    <script src="foo.js"></script>
    <p>See ya!</p>
    </body>
    </html>
  • Result
    UI Thread
    JavaScript
    UI Update
    UI Update
    time
  • Result
    UI Thread
    foo.js
    See ya!
    Hello world!
    time
  • Result
    UI Thread
    Download
    See ya!
    Hello world!
    Parse
    Run
    time
    The UI thread needs to wait for the script to
    download, parse, and run before continuing
  • Result
    UI Thread
    Download
    See ya!
    Hello world!
    Parse
    Run
    Variable
    Constant
    Download time takes the longest and is variable
  • Translation:The page doesn't render while JavaScript is downloading, parsing, or executing during page load
  • <!doctype html>
    <html>
    <head>
    <title>Example</title>
    </head>
    <body>
    <script src="foo.js"></script>
    <p>Hello world!</p>
    <script src="bar.js"></script>
    <p>See ya!</p>
    <script src="baz.js"></script>
    <p>Uh oh!</p>
    </body>
    </html>
  • Result
    UI Thread
    JavaScript
    UI Update
    UI Update
    JavaScript
    JavaScript
    time
    The more scripts to download in between UI
    updates, the longer the page takes to render
  • Technique #1: Load scripts dynamically
  • Basic Technique
    var script = document.createElement("script"),
    body;
    script.type = "text/javascript";
    script.src = "foo.js";
    body.insertBefore(script, body.firstChild);
    Dynamically loaded scripts are non-blocking
  • Downloads no longer block the UI thread
  • <!doctype html>
    <html>
    <head>
    <title>Example</title>
    </head>
    <body>
    <p>Hello world!</p>
    <script src="foo.js"></script>
    <p>See ya!</p>
    </body>
    </html>
  • Using HTML <script>
    UI Thread
    Download
    See ya!
    Hello world!
    Parse
    Run
    time
  • <!doctype html>
    <html>
    <head>
    <title>Example</title>
    </head>
    <body>
    <p>Hello world!</p>
    <script>
    var script = document.createElement("script"),
    body = document.body;
    script.type = "text/javascript";
    script.src = "foo.js";
    body.insertBefore(script, body.firstChild);
    </script>
    <p>See ya!</p><!-- more content -->
    </body>
    </html>
  • Using Dynamic Scripts
    UI Thread
    See ya!
    Hello world!
    UI Update
    Run
    time
    Download
    Parse
    Only code execution happens on the UI thread,
    which means less blocking of UI updates
  • function loadScript(url, callback){var script = document.createElement("script"), body = document.body;script.type = "text/javascript";
    if (script.readyState){ //IE <= 8 script.onreadystatechange = function(){if (script.readyState == "loaded" || script.readyState == "complete"){ script.onreadystatechange = null; callback(); } };} else { //Others script.onload = function(){ callback(); };}script.src = url;body.insertBefore(script, body.firstChild);
    }
  • Usage
    loadScript("foo.js", function(){
    alert("Loaded!");
    });
  • Timing Note:Script execution begins immediately after download and parse – timing of execution is not guaranteed
  • Technique #2: Defer scripts
  • <!doctype html>
    <html>
    <head>
    <title>Example</title>
    </head>
    <body>
    <p>Hello world!</p>
    <script defer src="foo.js"></script>
    <p>See ya!</p>
    <!-- even more markup -->
    </body>
    </html>
  • Support for <script defer>
    ?
    5.0
    3.5
    7.0
    4.0
  • Deferred scripts begin to download immediately, but don't execute until all UI updates complete
  • Using <script defer>
    UI Thread
    See ya!
    Hello world!
    More UI
    Run
    More UI
    time
    Download
    Parse
    Similar to dynamic script nodes, but with a
    guarantee that execution will happen last
  • Timing Note:Although scripts always execute after UI updates complete, the order of multiple <script defer> scripts is not guaranteed across browsers
  • Technique #3: Asynchronous scripts
  • <!doctype html>
    <html>
    <head>
    <title>Example</title>
    </head>
    <body>
    <p>Hello world!</p>
    <script async src="foo.js"></script>
    <p>See ya!</p>
    <!-- even more markup -->
    </body>
    </html>
  • Support for <script async>
    ?
    5.0
    3.6
    7.0
    10
  • Asynchronous scripts behave a lot like dynamic scripts
  • Using <script async>
    UI Thread
    See ya!
    Hello world!
    UI Update
    Run
    time
    Download
    Parse
    Download begins immediately and execution is
    slotted in at first available spot
  • Note:Order of execution is explicitly not preserved for asynchronous scripts
  • Runtime TechniquesWays to ensure JavaScript doesn't run away
  • function processArray(items, process, callback){
    for (var i=0,len=items.length; i < len; i++){
    process(items[i]);
    }
    callback();
    }
  • Technique #1: Timers
  • //create a new timer and delay by 500ms
    setTimeout(function(){
    //code to execute here
    }, 500);
    setTimeout() schedules a function to be added to the UI queue after a delay
  • function timedProcessArray(items, process, callback){
    //create a clone of the original var todo = items.concat();
    setTimeout(function(){
    var start = +new Date();
    do {
    process(todo.shift());
    } while (todo.length > 0 &&
    (+new Date() - start < 50));
    if (todo.length > 0){
    setTimeout(arguments.callee, 25);
    } else {
    callback(items);
    }
    }, 25);
    }
  • When Clicked
    UI Thread
    time
    UI Queue
    UI Update
    onclick
    UI Update
  • When Clicked
    UI Thread
    UI Update
    time
    UI Queue
    onclick
    UI Update
  • When Clicked
    UI Thread
    onclick
    UI Update
    time
    UI Queue
    UI Update
  • When Clicked
    UI Thread
    UI Update
    UI Update
    onclick
    time
    UI Queue
  • After 25ms
    UI Thread
    UI Update
    UI Update
    onclick
    time
    UI Queue
    JavaScript
  • After 25ms
    UI Thread
    JavaScript
    UI Update
    UI Update
    onclick
    time
    UI Queue
  • After Another 25ms
    UI Thread
    JavaScript
    UI Update
    UI Update
    onclick
    time
    UI Queue
    JavaScript
  • After Another 25ms
    UI Thread
    JavaScript
    JavaScript
    UI Update
    UI Update
    onclick
    time
    UI Queue
  • Technique #2: Script Yielding
    NEW!
  • //delay a function until after UI updates are done
    setImmediate(function(){
    //code to execute here
    });
    setImmediate() adds code to the UI queue after pending UI updates are finished
  • Support for Script Yielding
    ?
    ?
    ?
    ?
    10
    msSetIntermediate()
  • functionyieldingProcessArray(items, process, callback){
    //create a clone of the originalvartodo = items.concat();
    setImmediate(function(){
    var start = +new Date();
    do {
    process(todo.shift());
    } while (todo.length > 0 &&
    (+new Date() - start < 50));
    if (todo.length > 0){
    setImmediate(arguments.callee);
    } else {
    callback(items);
    }
    });
    }
  • When Clicked
    UI Thread
    time
    UI Queue
    UI Update
    onclick
    UI Update
  • When Clicked
    UI Thread
    UI Update
    time
    UI Queue
    onclick
    UI Update
  • When Clicked
    UI Thread
    onclick
    UI Update
    time
    UI Queue
    UI Update
  • When Clicked
    UI Thread
    UI Update
    UI Update
    onclick
    time
    UI Queue
  • After Last UI Update
    UI Thread
    UI Update
    UI Update
    onclick
    time
    UI Queue
    JavaScript
  • After Last UI Update
    UI Thread
    JavaScript
    UI Update
    UI Update
    onclick
    time
    UI Queue
  • No Other UI Updates
    UI Thread
    JavaScript
    UI Update
    UI Update
    onclick
    time
    UI Queue
    JavaScript
  • No Other UI Updates
    UI Thread
    JavaScript
    JavaScript
    UI Update
    UI Update
    onclick
    time
    UI Queue
  • Technique #3: Web Workers
  • Support for Web Workers
    10.6
    4.0
    3.5
    4.0
    10
  • Web Workers
    Asynchronous JavaScript execution
    Execution happens outside the UI thread
    Doesn’t block UI updates
    Data-Driven API
    Data is serialized going into and out of the worker
    No access to DOM or BOM
    Separate execution environment
  • //in page
    var worker = new Worker("process.js");
    worker.onmessage = function(event){
    useData(event.data);
    };
    worker.postMessage(values);
    //in process.js
    self.onmessage = function(event){
    var items = event.data;
    for (var i=0,len=items.length; i < len; i++){
    process(items[i]);
    }
    self.postMessage(items);
    };
  • When Clicked
    UI Thread
    time
    UI Queue
    UI Update
    onclick
    UI Update
  • When Clicked
    UI Thread
    UI Update
    time
    UI Queue
    onclick
    UI Update
  • When Clicked
    UI Thread
    onclick
    UI Update
    time
    UI Queue
    UI Update
  • When Clicked
    UI Thread
    onclick
    UI Update
    time
    UI Queue
    Worker Thread
    UI Update
  • When Clicked
    UI Thread
    UI Update
    UI Update
    onclick
    time
    UI Queue
    Worker Thread
    JavaScript
  • Worker Thread Complete
    UI Thread
    UI Update
    UI Update
    onclick
    time
    UI Queue
    onmessage
  • Worker Thread Complete
    UI Thread
    onmessage
    UI Update
    UI Update
    onclick
    time
    UI Queue
  • Recap
  • The browser UI thread is responsible for
    both UI updates and JavaScript execution
    Only one can happen at a time
  • Responsive UI
    UI Thread
    JavaScript
    UI Update
    UI Update
    time
  • Unresponsive UI
    UI Thread
    JavaScript
    UI Update
    UI Update
    time
  • Avoid Slow Loading JavaScript
    Dynamically created scripts
    Deferred scripts
    Asynchronous scripts
  • Avoid Slow JavaScript
    Don't allow JavaScript to execute for more than 50ms
    Break up long JavaScript processes using:
    Timers
    Script Yielding (future)
    Web Workers
  • Etcetera
    My blog: www.nczonline.net
    Twitter: @slicknet
    These Slides: slideshare.net/nzakas
    Hire us: projects@stubbornella.org
  • Questions?
  • Creative Commons Images Used
    http://www.flickr.com/photos/lrargerich/3115367361/
    http://www.flickr.com/photos/hippie/2406411610/
    http://www.flickr.com/photos/55733754@N00/3325000738/
    http://www.flickr.com/photos/eurleif/255241547/
    http://www.flickr.com/photos/off_the_wall/3444915939/
    http://www.flickr.com/photos/wwarby/3296379139/
    http://www.flickr.com/photos/derekgavey/4358797365/
    http://www.flickr.com/photos/mulad/286641998/
    http://www.flickr.com/photos/torley/2361164281/
    http://www.flickr.com/photos/ottoman42/455242/
    http://www.flickr.com/photos/goincase/3843348908/