Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Memory issues #7

Open
Tiago-Ling opened this issue Apr 16, 2016 · 0 comments
Open

Memory issues #7

Tiago-Ling opened this issue Apr 16, 2016 · 0 comments

Comments

@Tiago-Ling
Copy link
Owner

Currently the tilemap is using too much memory: a big map (e.g. 1000 x 1000 tiles or bigger) must create one 2D array of its size to each layer. This takes up a lot of memory which prevents usability for maps of this size. In my work computer a 1200x1200 map crashes the application (i suppose there's a memory use threshold ~1GB)

One possible way is to research more about sparse array optimization and compression: http://www.cs.nthu.edu.tw/~ychung/journal/ekmr_compression.pdf

The idea of this issue is to discuss smarter ways of storing map data during runtime.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant