Concurrent Mode in Angular- Non-blocking UIs at scale
summary
Explains how to make Angular rendering non-blocking by moving work off the main task, with concrete techniques and measurements: wrapping bootstrap in setTimeout to split a long task, replacing ngFor/ngIf with rx4 and rxLet to chunk rendering, and using the rx-angular cdk scheduling primitives. Claims show case studies and flame-chart comparisons: many red frame drops disappear, initial heavy tasks shrink by about 50 milliseconds, and interactive navigation becomes smooth.
AI-written summary · about
chapters (8)
- 0:00Start
- 0:50Compare Server Side and Client-Side Rendering
- 1:59What a Blocked Ui Means
- 5:59How Does Scheduling Work for Browsers
- 9:17User Interactions
- 11:36Frame Drop
- 14:42Reduce Dropped Frames
- 27:54The Rx Led Directive
related talks
29mPartially Zoneless - Performance tunning without Big Bang Refactorings
34mHigh-Performance Applications with Angular
23mPartially Zoneless Performance tuning without big bang refactoring
35mPerformance at Scale
33mPerceived faster Angular applications
45mReactive Frontends with RxJS and Angular
21mPartially Zone-Less
41mSpeeding Up Your Angular App: Techniques for Optimizing Rendering Performance
