~/talk

Demystifying JS Engines

Talkat CascadiaFest 2016 · 2016-08-03..08-05· [javascript, web-performance]
links:none on file
slides:none on file

Explains how modern JS engines parse to bytecode, collect runtime type feedback and run multi‑tier JITs: SpiderMonkey uses Baseline → Ion; V8 adds an interpreter plus Crankshaft and Turbofan; JavaScriptCore moves code through Baseline, DFG, then FTL and uses LLVM/B3. Lists concrete thresholds (JSC: statement >100 or function >6 for baseline, >1,000/66 for DFG, >10,000 for FTL), shows optimizations like loop-invariant code motion, inlining and dead‑code elimination, and covers generational/incremental GC and the 50× microbenchmark anomaly.

AI-written summary · about

  1. 0:00Introduction
  2. 1:37History of JS Engines
  3. 5:18Architectures
  4. 11:53Optimizations
  5. 13:42Dead Code Elimination
  6. 14:19Garbage Collection
  7. 16:28Conclusion
~/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.