Optimizing Performance of Web Apps: Removing Bottlenecks for a Better Experience
summary
A demo web app on a 512 MB Heroku-like box hits OOM from server-side UI state; using VisualVM and a Playwright opener reveals ~1 MB per chart and 21 simultaneous windows, fixed by nulling the chart configuration via reflection so the heap stays under 32 MB Heap and OOMs stop. A salaries page shows a 12 s DB request; enabled lazy loading (Grid callback + progress indicator) and reduced DB roundtrips. An 8 s Safari render for 80 rich editors becomes ~162 ms by rendering 5 items and loading more on scroll.
AI-written summary · about
chapters (7)
- 0:00Introduction to optimization
- 7:50Demo of the application
- 13:36Memory consumption analysis
- 20:56Database query bottlenecks
- 31:33UI rendering performance issues
- 40:36Key takeaways and summary
- 43:05Q&A session
related talks
30mWeb runtime performance
22mPerformance Empathy
34mOptimizing Performance in Large-Scale React & Node.js Applications
01h 03mSpeed up your Web Application
37mSecret Shortcuts of Loading Web Performance
32mPractical Performance Tips Building Progressive Web Apps
29mClient Says Your Awesome Web App Works Slowly. Now What?
47mReact, Rendering, Performance