Improve the memory usage in Ember
Ember currently really gobbles up a lot of memory. This is mainly caused by not releasing memory used for stuff like the terrain etc, and also not unloading unused textures and meshes. We need to optimize the terrain handling so that unused Mercator structures are unloaded. We probably need to have some kind of cache mechanism where we keep those structures that are used the most (i.e. those segments that are closest to the camera) around though.
It also preloads all resources at start up, which is nice since it doesn't cause any slowdowns when ingame and loading resources, but it also means that it puts a lot of unused resources in memory. In order to alter this to instead load resources on demand we however need to implement background resource loading, which is a whole other blueprint.
Blueprint information
- Status:
- Started
- Approver:
- Erik Ogenvik
- Priority:
- Medium
- Drafter:
- Erik Ogenvik
- Direction:
- Needs approval
- Assignee:
- Erik Ogenvik
- Definition:
- Approved
- Series goal:
- None
- Implementation:
-
Deployment
- Milestone target:
- None
- Started by
- Erik Ogenvik
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
I've closed up a couple of glaring memory holes, mainly related to how images (for shadows, splatting etc.) are handled.
Still haven't found the cause of the continuous leak of 4-6kbps, is such a leak really exists.
Is fixing a bug "Memory leaks at 4kb/s" closes this blueprint, or other issues still standing?
//alex
Well, to some degree. But there are other issues left, such as unloading of resources, which also needs to be handled. /erik
I'll make this milestone independent and decrease the importance. It's still an ongoing job, but since there's no known memory leaks or hideously inefficient allocations we'll put it on the back burner for now. /erik
