1 / 11

Google I/O 2010 Notes Talk: Measure in milliseconds redux: Meet Speed Tracer

Google I/O 2010 Notes Talk: Measure in milliseconds redux: Meet Speed Tracer. Notes by: Armando Padilla. Disclaimer!!!.

lavender
Download Presentation

Google I/O 2010 Notes Talk: Measure in milliseconds redux: Meet Speed Tracer

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Google I/O 2010 NotesTalk: Measure in milliseconds redux: Meet Speed Tracer Notes by: Armando Padilla

  2. Disclaimer!!! • These are only notes that I took during the talk. I take no ownership of the material presented during the talk. Again these are solely my notes I took during the talk. If I made a mistake in what’s presented here that’s just my mistake due to my poor note taking skillz. With legal out of the way…Let’s Continue…

  3. Measure in milliseconds redux: Meet Speed Tracer Abstract from Talk: It turns out that web apps can be slow for all sorts of opaque and unintuitive reasons. Don't be fooled into thinking that bloated, slow JavaScript is the only culprit. This session introduces you to Speed Tracer, a new GWT tool that can tell you exactly where time is going within the browser. Tools Used & Featured: Speed Tracer.

  4. Why performance matters • Affects users impression of the application. • Users are very sensitive to delays. • User perception of quality changes as the performance is degradatted.

  5. The Magic Number! • 100ms • Threshold in which a user remains satisfied with the application. • Above 100ms user leaves or becomes dissatisfied with application.

  6. So where’s are the problems? • We don’t measure. • Measuring our application is infrequently done. • Blame it on the browser. • Browsers use special tweaks to speed up loading of JS, CSS, etc. Not all browsers apply them the same… So we run into problems.

  7. Where are the bottlenecks? • Network. • Amount of data transferred. • How is the browser behaving?

  8. Solution! Speed Tracer. • Informs what the browser is doing and times your application. • Ability to share data with other developers by saving it. • Allows us to zoom into specified request and receive detailed information about the request down to what the Browser is doing. • http://code.google.com/webtoolkit/speedtracer/

  9. Speed Tracer NEW Feature! • Latest release informs you of the line of code that is causing the issue. • Clicking on the warning will open your code and show you the line on your code. • Only available when using it with GWT.

  10. Additional Notes • App Engine Integration • Displays information on what a request is doing at the server level.

  11. Google & CI • In use at Google. • Speed Tracer fully integrated. • New commits trigger a speed audit using Speed Tracer.

More Related