Performance, Flexibility, Customization by Roman Enikeev (Rus) | JSConfAM19
summary
Migrated a heavy realtime dashboard from jQuery server‑side filtering to a client‑loaded JSON model (~10k rows, >3MB) with updates via WebSocket, rewrote the UI in Angular on an ASP.NET Core backend, and optimized performance by using OnPush change detection, a pooled single‑row component with custom virtual scrolling to reduce DOM mutations, and measured browser rendering vs scripting work—cutting initial load from ~8s to ~2–3s and making IE11 scroll 10k rows faster than Chrome.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 2:41Frontend evolution and Angular
- 4:29Problem statement and solutions
- 6:14Server to client rendering
- 9:05Client-side big data storage
- 10:47Angular performance issues
- 13:14Browser rendering and scripting
- 16:27DOM optimization and legacy
- 17:50Virtual scrolling solution
- 20:16Optimized row component
- 22:25Testing and results
- 23:29Low-level browser sync
- 25:38Q&A
related talks
29mHow we did everything wrong and got away with it (Angular success story)
43mAngular and React: friends learning from each other
31mMobile-friendly web apps with Angular
31mThe Need for Speed (aka Angular Performance).
20mAngular Performance in the Enterprise
40mOptimizing an Angular application
28mAngular Renaissance
40mNon-trivial optimization techniques in Angular