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 Use / Variable Size #11

Open
MatthewClarkMay opened this issue Feb 15, 2017 · 3 comments
Open

Memory Use / Variable Size #11

MatthewClarkMay opened this issue Feb 15, 2017 · 3 comments

Comments

@MatthewClarkMay
Copy link
Owner

MatthewClarkMay commented Feb 15, 2017

One of the big issues with DataServer.py is that memory is constantly consumed. Variables are ever growing, and this needs to change, so maybe we should use a database? I'm thinking we incorporate mongodb, and track metrics there. That way variables aren't tracking metrics the entire time, and we save on memory space.

Thoughts/Ideas?

@MatthewClarkMay MatthewClarkMay changed the title Variable size Memory Use / Variable Size Feb 15, 2017
@diegodblr
Copy link
Contributor

Yes ... the created objects are huge and store numeric data that could be in a database. This will make it easier to generate reports. Good idea. A simple bank I use here is SQLITE. One more option.

@MatthewClarkMay
Copy link
Owner Author

I've been learning more about Redis, and would like to withdraw my MongoDB statement. In upcoming days/weeks I will begin working on an implementation that tracks stats using Redis. It will still be in memory, but we can control how large we want data sets to grow, persistence, and speed.

@diegodblr
Copy link
Contributor

I disabled the console.log of the code and solved the browser memory problem here. It's been working for days without crashing.

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

2 participants