~/talk

JavaScript & Metaperformance

Talkat Velocity 2011 · 2011-06-14..06-16· [javascript, web-performance]
slides:none on file

Argues that tuning engines to synthetic tests encourages bad coding patterns and instead creates a new, representative benchmark: JSLint running on itself to measure real JavaScript behavior. Reports concrete numbers — V8 (Chrome) is initially 3–5× slower than Safari and IE10 preview on that workload — and shows the practical result: engine teams deliver a fivefold V8 improvement in about two weeks (Chrome 13 Canary), proving targeted benchmarks change implementation choices.

AI-written summary · about

  1. 0:00Start
  2. 2:18No time for Optimizing
  3. 6:15Lies, Damn Lies, and Benchmarks
  4. 7:34Life on the Web
  5. 8:24The DOM Bottleneck
  6. 10:46This behavior of developers interacts badly with performance benchmarks. • Benchmarks
  7. 12:55I designed a new benchmark.
~/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.