koobas.hobune.stream
Multiple small update calls vs one large update call?
I am having performance related issues with my 3D game for anroid although my batches go upto max 35. In my game scene I have one script that uses Update() for movement of movement of some gameobjects. It is applied to more than 100 gameobject seperately so there are more than a 100 update calls for that script. Is it an acceptable approach or should I write a script that alone manages movement of all those gameobjects (using array or something like that) in one large update? Thanks!
Surely it is acceptable. 100 update calls are so negligible. If you need to move objects separately(independently) so use separate updates else use one update for it. It is better that use less update calls but it is not readable and hard for debugging.
Thanks for your answer. Yes, I wrote another script that alone implements movement of all gameobjects and but the difference in CPU usage (in terms of time ms in profiler) was almost none.
Does is hold true for many(100+) different scripts everyone having its own update function?
