Optimizing Legacy Web UIs Inside a AAA Game Engine
summary
How to make legacy Web UIs run smoothly inside a AAA game engine (Flight Simulator 2024) by profiling WebKit and JS to find bottlenecks, fixing memory leaks so UIs can run for hours, and reducing heavy CSS, excessive async patterns, oversized assets and noisy polyfills. The talk gives concrete optimization techniques and trade-offs for frontend choices (e.g., recommending BEM, warning against transpiled getter/setters) while avoiding changes that would break the game engine or players’ experience.
AI-written summary · about
chapters (13)
- 0:00Web optimization in AAA engine
- 1:31Engine constraints
- 5:21Performance issues
- 9:11Custom WebKit profiler
- 11:41Optimization patterns
- 16:52DOM node virtualization
- 20:27Async handling
- 26:55Text and DOM updates
- 31:31JS type pitfalls
- 36:27Maps vs objects memory
- 37:53Memory leak detection
- 40:20Minification and build
- 42:25Conclusion
related talks
40mHow to Improve JavaScript Performance
24mOptimizing and Building UI for AAA Games
44mSponsored session: Progressive Web Games
47mOptimising for the Web
20mOptimizing assets for graphics heavy Web Applicatoins: tips and tricks from the game dev background
21mEvolution of Web Performance
58mNeed for speed 8, performance tuning of your web application
01h 03mSpeed up your Web Application