You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the Code-Only Tutorials, I discovered that Stride's startup RAM usage is around 90MB. Then using the Drag/Drop Sample, adding 1000 cubes increases RAM usage to 148MB (+58MB per 1000 boxes == 58KB per box).
Can we reduce the RAM cost per box? (not sure if this requires a change to the sample code, or to Stride3D source code)
58KB/box seems high, when a competing engine does this for 18KB/box. Currently, Stride's sample has 3X the ram cost.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
In the Code-Only Tutorials, I discovered that Stride's startup RAM usage is around 90MB. Then using the Drag/Drop Sample, adding 1000 cubes increases RAM usage to 148MB (+58MB per 1000 boxes == 58KB per box).
Can we reduce the RAM cost per box? (not sure if this requires a change to the sample code, or to Stride3D source code)
58KB/box seems high, when a competing engine does this for 18KB/box. Currently, Stride's sample has 3X the ram cost.
Beta Was this translation helpful? Give feedback.
All reactions