# [Understanding your render graph](https://learn.arm.com/learning-paths/mobile-graphics-and-gaming/render-graph-optimization/understanding-your-render-graph/)

## In this learning path

- [Introduction](https://learn.arm.com/learning-paths/mobile-graphics-and-gaming/render-graph-optimization/)
- [What are render graphs?](https://learn.arm.com/learning-paths/mobile-graphics-and-gaming/render-graph-optimization/what-are-render-graphs/)
- [Generating a render graph for your application](https://learn.arm.com/learning-paths/mobile-graphics-and-gaming/render-graph-optimization/generating-a-render-graph-for-your-application/)
- [Understanding your render graph](https://learn.arm.com/learning-paths/mobile-graphics-and-gaming/render-graph-optimization/understanding-your-render-graph/)
- [Problem solving – unused resources](https://learn.arm.com/learning-paths/mobile-graphics-and-gaming/render-graph-optimization/unused-resources/)
- [Problem solving – unwanted execution nodes](https://learn.arm.com/learning-paths/mobile-graphics-and-gaming/render-graph-optimization/unwanted-execution-nodes/)
- [Problem solving – textures with excessive resolution](https://learn.arm.com/learning-paths/mobile-graphics-and-gaming/render-graph-optimization/textures-with-excessive-resolution/)
- [Problem solving – inefficient transfer workloads](https://learn.arm.com/learning-paths/mobile-graphics-and-gaming/render-graph-optimization/inefficient-transfer-workloads/)
- [Next Steps](https://learn.arm.com/learning-paths/mobile-graphics-and-gaming/render-graph-optimization/_next-steps/)

## Components of a render graph
Here’s the graph from the previous section:

![An inefficient render graph in need of optimization](https://learn.arm.com/learning-paths/mobile-graphics-and-gaming/render-graph-optimization/inefficient-render-graph.svg)  
*An inefficient render graph in need of optimization*

At a basic level, render graphs consist of *boxes* and *arrows*:

- Boxes, formally called *nodes*, represent rendering operations and resources. Nodes for rendering operations are formally called *execution nodes*.
- Arrows, formally called *edges*, show the movement of data between rendering operations.

Render graphs describe rendering performed by the GPU while it is constructing a single frame. This rendering starts and ends with resources. As a result of graphs being read from left to right:

- The leftmost nodes represent the rendering of input resources, such as one or more textures.
- The rightmost nodes represent the final outputs of the rendering.

> To keep the graph as simple as possible, Frame Advisor omits read-only resources.

In an efficiently-generated frame, all workloads and generated resources contribute to the creation of the final [swapchain](https://en.wikipedia.org/wiki/Swap_chain) output image shown on the right of the diagram. Notice in the graph above that the swapchain is shown in a different color.

In a suboptimally-generated frame, there may be other outputs which are not sent to the swapchain and consequently are not shown to a user. These represent unwanted data movement.

## Graph nodes in detail
Take a closer look at what can be represented in a node on the render graph.

### Render passes
Most of the execution nodes in the sample graph above are colored green and labeled “RP…” These are [render passes](https://developer.arm.com/documentation/102479/0100/How-Render-Passes-Work).

![A render pass node](https://learn.arm.com/learning-paths/mobile-graphics-and-gaming/render-graph-optimization/render-pass-node.png)  
*Figure 2. A render pass node*

Render passes transform sets of input images into sets of output images using a rendering pipeline. The way this is declared varies across APIs. In OpenGL ES, [a number of different API calls](https://developer.arm.com/documentation/102479/0100/How-Render-Passes-Work/Render-Passes-in-OpenGL) can indicate the boundaries of a render pass. In Vulkan, [render passes are declared explicitly](https://docs.vulkan.org/spec/latest/chapters/renderpass.html).

Within each execution node representing a render pass, Frame Advisor gives information such as:

- The resolution of the texture being rendered
- A list of the attachments provided to the render pass and the name of each of these attachments.
- The number of API draw calls within the render pass.

> When you click an execution node, such as a render pass, Frame Advisor navigates to the associated API call.

### Other types of execution node
The graph also shows a transfer node, colored blue, and labeled “Tr…”.

![A transfer node](https://learn.arm.com/learning-paths/mobile-graphics-and-gaming/render-graph-optimization/transfer-node.png)  
*A transfer node*

Transfer nodes represent data movement between resource locations in memory.

You may also see other types of execution node. For example, you may see compute nodes if your application uses compute shaders.

### Resource nodes
Resource nodes show inputs and outputs of the execution nodes. They are shown as small grey rectangles with rounded edges.

There are different types of resource node:

- The swapchain: this represents the output of the computation. There is one swapchain on every graph.  
  ![A swapchain node](https://learn.arm.com/learning-paths/mobile-graphics-and-gaming/render-graph-optimization/swapchain-node.png)  
  *A swapchain node*

- [Textures](https://www.khronos.org/opengl/wiki/Texture): these are marked with a leading letter `T`.  
  ![A node for texture 1](https://learn.arm.com/learning-paths/mobile-graphics-and-gaming/render-graph-optimization/texture-node.png)  
  *A node for texture 1*

- [Render buffers](https://www.khronos.org/opengl/wiki/Renderbuffer_Object): Like textures, these represent images. The title of render buffer nodes begins with letters `RB`. The title ends with a code indicating the class of render buffer – for example, `.s` for stencil and `.d` for depth.  
  ![A node for render buffer 1, representing depth](https://learn.arm.com/learning-paths/mobile-graphics-and-gaming/render-graph-optimization/render-buffer-node.png)  
  *A node for render buffer 1, representing depth*

The original render graph also contains a render buffer node representing a stencil.