Render Optimization

Render optimizations are methods and techniques that aim to improve render times, render quality, or sometimes a combination of both. These include modifying the behavior of the engine or modifying the scene itself.

Optimizing Scenes

In many cases, optimizing the actual scene itself can improve render times or quality. Some of these include:

• Reducing geometry, or optimizing topology (e.g. using quads instead of n-gons)
• Reducing texture sizes (e.g. using 2K textures instead of 4K)
• Adequate routes for light paths (e.g. large gaps)
• Avoiding complex materials or adjusting materials to behave differently (e.g. archviz glass)
• Reducing resolution of the final render

Optimizing Engine Behavior

Often times optimizing an engine's behavior can also allow for reducing render times or scene quality. Some examples include:

• Limiting light bounces, or even approximating lighting through alternate means
• Adjusting sample count for ray tracing engines, often in conjunction with [Denoiser|denoising algorithms]]
• Adjusting shadow resolution for rasterized engines

Software/Engine Specific Recommendations

The following are recommendations for specific programs or render engines. Depending on the scene, these may or may not need to be adjusted.

Cycles (Blender)

Although Cycles is one of the faster path tracing engines, there's some options that can be adjusted for performance.

Sampling

Beyond adjusting the sample count, there are alternate settings in Cycles specifically related to sampling. In particular, adjusting adaptive sampling settings to kick in earlier on can reduce render times, at the cost of more noise. Setting the noise threshold to $0.03$ instead of $0.01$ may be a good compromise of quality and render times.

Another sampling related setting in Cycles is light tree, which reduces noise in scenes with a heavy amount of lights, but may cause more noise in scenes with fewer lights.

Light Paths

Adjusting light path settings can also be another source of performance and/or quality improvement. This can be in the form of adjusting light bounces, volumetric stepping, or clamping bright pixels.

By default, Cycles sets its max light bounces to $12$, which may be excessive in many cases. Lowering to $8$ often creates little to no difference, while reducing render times.

Some scenes may allow for reducing max light bounces further down to $4$ or even $3$. However, it should be noted that adjustments the range of $1$ to $5$ typically introduce larger changes to the scene than higher ranges.

In addition to max light bounces, there is also stepping rate and max steps. Stepping rate defines how many "steps" is performed in a volumetric object, where lower values allow for more detail, at the cost of render time, and max steps defines how many steps Cycles will perform for volumes before giving up. Depending on the scene, the default value of $1$ may be excessively low, and increasing the rate may allow for performance improvements. In addition, decreasing max steps may also improve render times, at the cost of detail.

Like many path tracers, Cycles includes options to clamp the brightness of pixels caused by both direct and indirect bounces. When set to $0$, no clamping is done. While clamping direct lighting is usually not necessary, clamping indirect lighting may reduce the amount of fireflies created when rendering. However, clamping indirect can often reduce the brightness of highlights on reflective objects.

Cycles also includes options to disable caustics. However, disabling these will drastically change lighting if a scene contains many reflective objects.

Fast GI approximation can also improve render times, though it can also drastically change how a scene looks.