~/talk

Performance Tuning Secrets

Talkat JSConf US 2013 · 2013-05-28..05-30· [web-performance, web-platform]
links:none on file
slides:none on file

Browser-side profiling uses concrete tools and measurable claims: Chrome tracing and the DevTools flame chart expose thread-by-thread timings, the Telemetry framework automates timeline captures, and the chrome tracing view plus FPS meter reveal render vs JavaScript bottlenecks. V8 logs and plot-timer events show GC (scavenger vs compactor) and optimized vs deoptimized code; automated traces plus 600 fps camera video quantify rendering latency (keypress-to-paint delays). Real app data comes from projects like 100,000 lines of JavaScript Brackets and Topcoat; these techniques work and locate actionable bottlenecks.

AI-written summary · about

  1. 0:00Introduction to tuning
  2. 1:49Performance challenges
  3. 3:30Timeline panel features
  4. 5:59Advanced rendering tools
  5. 8:09Chrome tracing internals
  6. 12:34High-speed camera hack
  7. 14:26Memory profiling
  8. 16:18CPU profiling methods
  9. 19:09V8 engine log analysis
  10. 26:13Strategic performance focus
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.