mhulse / 3d-wiki Goto Github PK

Move code out of loops when possible

Loops are a common place for inefficiencies to occur, especially when they are nested. If a loop runs frequently on many GameObjects, efficiency will decrease.



Consider whether code must run every frame

The Update() function runs every frame. Use Update() for code that must  change often. Otherwise, move code out of Update() so that it runs only when it needs to.

 

Run code every [x] frames

For code not trigged by an event, you can choose to run it every [x] frames. The following example runs ExampleFunction every 3 frames.



private int interval = 3;

 

void Update()

{

    if (Time.frameCount % interval == 0)

    {

        ExampleFunction();

    }

}

 

Reduce use of GetComponent()

Storing and reusing function results is efficient. This technique is known as caching.

GetComponent() is a good opportunity to cache and increase optimization.

The following code calls GetComponent() only once, as the result of the function is cached. The cached result can be reused in Update() without any further calls to GetComponent() .



private ExampleComponent componentName;

 

void Start()

{

    componentName = GetComponent<ExampleComponent>();

}

 

void Update()

{

    ExampleFunction(componentName);

}

 

Use object pooling

Object pooling temporarily deactivates, recycles, and reactivates objects as needed. This is more efficient than instantiating and destroying objects.