Optimize performance of moving elements at runtime
When you move a large amount of elements at runtime, performance optimization is crucial, especially for applications requiring smooth and responsive interactions.
Certain CSS properties, such as top, left, width, height, or flex, can trigger layout recalculations when updated. These recalculations dirty the layout and might cascade updates across multiple elements, significantly impacting rendering performance. Use these properties sparingly and only when absolutely necessary.
Best practices for moving elements
The most performance-efficient way to move elements is to use the style.translate property. This property adjusts an element’s position dynamically without recalculating the layout. Unlike other positioning methods, style.translate operates at the transform stage. It minimizes the computational overhead and improves rendering performance by reducing dependency on CPU-intensive processes.
Use usage hints to reduce draw calls and geometry regeneration
To further enhance performance, leverage usage hints to optimize how elements are processed during runtime. Usage hints help:
- Reduce draw calls.
- Avoid unnecessary geometry regeneration.
If the transform of the element, such as position, rotation, or scale, changes frequently, set usage hint to DynamicTransform. This pushes transform updates directly to the GPU, bypassing CPU meshThe main graphics primitive of Unity. Meshes make up a large part of your 3D worlds. Unity supports triangulated or Quadrangulated polygon meshes. Nurbs, Nurms, Subdiv surfaces must be converted to polygons. More info
See in Glossary updates and improving performance.
You can set the usage hints in UI(User Interface) Allows a user to interact with your application. Unity currently supports three UI systems. More info
See in Glossary Builder, UXML, or C#. The following examples set the usage hints to DynamicTransform:
UXML:
<ui:VisualElement usage-hints="DynamicTransform" />
C#:
visualElement.usageHints = UsageHints.DynamicTransform;
The supported usage hints are:
Flow of updating and rendering a visual element
The following diagram illustrates the flow of updating and rendering a visual elementA node of a visual tree that instantiates or derives from the C# VisualElement class. You can style the look, define the behaviour, and display it on screen as part of the UI. More info
See in Glossary at runtime:
For an example that optimizes rendering and updates for frequently changing elements at runtime, refer to Move elements at runtime.