How to optimise Qt Quick 2 applications for maximum performance
summary
Shows how Qt Quick 2 renders via a scene graph and OpenGL, then gives concrete fixes: use GammaRay overdraw visualization and OpenGL profilers to find costly elements, enable layer.enabled caching to snapshot expensive shader effects, and reduce state changes so the engine can merge geometry — batching can turn many elements into one draw call while opacity breaks batching and clipping or small transforms explode draw counts. Benchmarks often show tens to hundreds of unnecessary draw calls; profile, cache, and hide invisible items.
AI-written summary · about
chapters (7)
- 0:00Introduction and speaker intro
- 6:48Detect and avoid overdraw
- 15:43Caching expensive elements
- 22:48Understanding OpenGL basics
- 33:35Minimize state changes
- 47:02Design pitfalls and fixes
- 51:03Q&A session
related talks
01h 10mPerformance: Do Graphics the Right Way
51mUsing the Qt Quick Scene Graph API
01h 02mCreating Performant Qt Quick Apps
52mAccelerating Qt WebKit Applications
46mWhat's new in QtQuick 2.0
46mGraphics performance - Best practices
54mCustomizing Qt to create first class graphical experiences on highly customized hardware
01h 02mUsing Qt Quick and the new Qt graphics stack, Scene Graph