Render graphs: declare dependencies and control resource lifetimes

Describe the frame as data flow

A renderer becomes difficult to modify when resource ownership is implicit. A post-processing pass may read an image that another feature unexpectedly overwrites, or keep a temporary texture alive for the whole frame. Start by describing each pass's inputs, outputs and externally visible effects. This contract makes a new feature's dependencies reviewable before its commands execute.

Separate declaration from execution

A render graph records passes and resource usage, then derives an execution plan. Unreal's RDG can cull unused work, manage transient resources and schedule synchronization. It distinguishes resources whose lifetimes remain inside the graph from external resources that survive outside it. [1] Declaring a read or write is a correctness obligation: an undeclared access gives the planner an incomplete account of the frame.

Work through an aliasing example

Consider four ordered passes. The first writes an 8 MiB temporary mask; the second consumes its final contents. Only afterward does the third create a 16 MiB blur intermediate, consumed by the fourth. If memory requirements are compatible and execution prevents overlapping use, the two temporary resources may share an idealized 16 MiB region instead of separate regions totaling 24 MiB.

This arithmetic excludes allocation overhead and every other frame resource. If the fourth pass also reads the original mask, their lifetimes overlap and the proposed reuse is invalid. CPU command-recording order alone is not proof that GPU accesses have finished. Inspect the actual resource timeline and dependencies.

Validate the resource contract

Name resources by purpose. Declare reads, writes and relevant subresources precisely, and define whether a newly allocated image must be cleared or fully overwritten. Keep temporal history and other persistent data under explicit external ownership.

Use graph visualization and API validation while enabling effects one at a time. Vulkan's synchronization guide describes pipeline barriers as controls on which stages must wait for earlier stages. [2] The graph must ultimately produce synchronization appropriate to the underlying API. Compare output with aliasing or asynchronous scheduling disabled when diagnosing corruption; treat the comparison as evidence, not a permanent fix.

Measure the scheduling tradeoff

Asynchronous compute can overlap independent work, but concurrent passes may compete for execution capacity or memory bandwidth. Their overlapping lifetimes can also reduce opportunities to reuse memory. Compare GPU duration, peak transient allocation and CPU recording cost on the target workload.

Keep resource histories from a normal frame, a resolution change and a disabled-effect transition. A graph that renders one screenshot correctly may still contain an uninitialized read or an unintended lifetime extension on another path. Optimize only after those paths have a clear ownership and initialization policy.

Sources

[1] Render Dependency Graph — Epic Games.

[2] Vulkan synchronization guide — Khronos Group.