Angular Performance Patterns
summary
Shows how to use Angular DevTools profiler to find real slowdowns and fixes: Plotly event listeners cause zone pollution and trigger ~740 ms change‑detection frames until initialization is moved with runOutsideAngular; typing triggers redundant checks across sibling lists and gets fixed with onPush + Immutable.js refs; expensive per-item Fibonacci recalculations become a pure calculate pipe; 25 ms checks on huge lists drop to about one fifth with cdk virtual scroll.
AI-written summary · about
chapters (6)
- 0:00Start
- 0:58Use Angular Devtools
- 6:03Zone Pollution Pattern
- 6:39Out of Bounds Change Detection
- 13:03Recap
- 13:39Recalculation of Referentially Transparent Expressions
related talks
31mAngular Performance: Your App at the Speed of Light
40mOptimizing an Angular application
20mAngular Performance in the Enterprise
34mHigh-Performance Applications with Angular
20mFaster Angular Applications
23mPerformance optimizations in Angular
12mAngular performance pitfalls and how to avoid them
26mProfiling Angular apps like a Shark
