16-02-2022, 09:17 AM
(This post was last modified: 16-02-2022, 09:17 AM by josemendez.)
Hi there!
Optimizations in 6.4 only affect memory allocation, should make no difference in raw performance. These optimizations are:
- Introduced a job handle pool to avoid runtime allocation of handles by both Burst and Oni backends. (instead of allocating new handles every frame, they're pooled).
- Constraint padding array in Burst solver has been turned into a member variable instead of allocating anew it every frame.
(instead of creating a new array every frame, it's created at startup and then populated every frame).
- Collision and friction batches are pooled instead of allocated every frame. (same as with job handles).
The rest of the engine remains unchanged. I've been unable to measure any significant performance differences between 6.2. and 6.4. Would it be possible for you to describe the scene in which you're testing this, and share a picture of Unity's profiler showing this issue?
thanks!
Optimizations in 6.4 only affect memory allocation, should make no difference in raw performance. These optimizations are:
- Introduced a job handle pool to avoid runtime allocation of handles by both Burst and Oni backends. (instead of allocating new handles every frame, they're pooled).
- Constraint padding array in Burst solver has been turned into a member variable instead of allocating anew it every frame.
(instead of creating a new array every frame, it's created at startup and then populated every frame).
- Collision and friction batches are pooled instead of allocated every frame. (same as with job handles).
The rest of the engine remains unchanged. I've been unable to measure any significant performance differences between 6.2. and 6.4. Would it be possible for you to describe the scene in which you're testing this, and share a picture of Unity's profiler showing this issue?
thanks!