Replies: 1 comment
-
Instead at v1.2.1, I've optimized by reusing already allocated arrays when the new device count matches the previous. Despite this, the native side still exhibits frequent array allocation and deallocation. Assuming 'every frame' implies a game context (approx. 60 FPS), 60 updates per second is overkill. Real-time feel can be maintained with just one update per second, and such refreshing should be limited to the settings screen |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Just a suggestion, but when UpdateDevicesInfo is called it allocates new arrays each time. I'm calling this method every frame of my app to update the device, so it would help a bit to pool
Beta Was this translation helpful? Give feedback.
All reactions