In this lesson, you will learn how to define and strictly enforce frame time budgets to ensure your high-end visual features do not compromise your target hardware’s performance.
When aiming for high-fidelity visuals—like complex Volumetric Clouds or detailed Nanite geometry—it is easy to exhaust your frame time before you even begin rendering gameplay elements. Establishing a performance budget is the act of deciding exactly how many milliseconds (ms) each subsystem is allowed to consume before you start development, rather than trying to optimize after the fact.
Defining the Budget
For a target of 60 FPS, your total frame budget is 16.67ms. However, you must reserve time for game logic, physics, and CPU overhead, which typically leaves roughly 10ms to 12ms for the GPU.
If you are pushing advanced features like Lumen and Volumetric Fog, you must assign "cost envelopes" to your visual systems:
- Base Rendering (Nanite/Shadows): 6ms
- Lighting/Lumen: 3ms
- Post-Processing/Translucency: 2ms
- Buffer/Safety Margin: 1ms
Enforcing the Budget
You enforce these budgets by using profiling tools like the GPU Visualizer (Ctrl + Shift + ,) to audit your current costs against your targets. If your "Post-Processing" category exceeds its 2ms budget, you know exactly which features to scale back or optimize using the r.ScreenPercentage or r.PostProcessAAQuality commands.
You can also use the stat console commands to monitor your budget in real-time during development:
stat unit
stat gpu
By keeping these metrics visible in your viewport, you create a "performance-first" culture. If you add a new Light Shaft effect, you must immediately check if it pushed your Lighting category over its 3ms allocation. If it did, you must either find a way to optimize that effect or trade off performance elsewhere—perhaps by reducing texture resolution or simplifying a Post-Process Material—to remain within the total budget.
Key Takeaway: A performance budget transforms optimization from a reactive "clean-up" phase into a proactive design constraint, ensuring your visual fidelity remains consistent across your entire project.