How to Improve Angular 2 Performance?
summary
A postmortem of optimizing a real Angular 2 application showing practical steps: enable tree-shaking, switch from JIT to AOT compilation, use Zone.js with proper OnDestroy cleanup to prevent leaks, prefer push change detection over many bindings, debounce inputs and cancel stale requests, and move data composition up using RxJS and a HATEOAS-style REST approach. These changes reportedly reduced the bundle from about 2 MB to a 600 KB build, removed memory leaks, and produced measurable improvements in load and response times after 128 hours of work.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:51Bundle size
- 8:37JIT vs AOT
- 12:35App architecture
- 15:02Binding efficiency
- 16:48Caching REST APIs
- 21:54Zone.js leaks
- 24:29Two-way binding
- 27:20Memory strategies
- 28:27DOM rendering
- 30:37Q&A
related talks
29mOptimizing Angular 2 Apps for Production
34mHigh-Performance Applications with Angular
31mOptimized Angular apps: smaller, faster, better
40mOptimized Angular Apps: Smaller, Faster, Better
20mTools for Fast Angular Applications
23mPerformance optimizations in Angular
19mTuning Your Angular Application
43mAngular Performance Workshop