Pragmatic performance patterns
summary
A concrete case study: an HTML-to-JSON pipeline gets a tiny synthetic benchmark and a benchmark-first workflow so changes are measured not guessed. Uses Node v6 inspector CPU profiler to inspect hotspots, a 1 ms pass/fail rule (1 ms threshold), and a targeted string-index/replace microfix that drops a critical step from 0.09 to 0.06. Swapping an HTML-encode package also saves measurable CPU time, proving the approach works.
AI-written summary · about
chapters (4)
- 0:00Start
- 5:291 MS FAIL!
- 10:41PERFORMANCE WAS A PRIORITY FROM THE BEGINNING
- 12:18WRITE BENCHMARKS ON PIECE OF THE CODE
related talks
16mJavaScript & Metaperformance
27mAnd Benchmarks for All!
59mProfiling JavaScript Like A Pro
40mPerformance Patterns
34mUnderstanding JavaScript Performance
01h 03mThe performance loop—A practical guide to profiling and benchmarking
46m10 secrets to improve Javascript Performance
57mPragmatic Performance: When to care about perf, and what to do about it