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

Django keeps data in cache with mem_opt = True #2

Closed
RicCapUnitn opened this issue Oct 20, 2017 · 2 comments
Closed

Django keeps data in cache with mem_opt = True #2

RicCapUnitn opened this issue Oct 20, 2017 · 2 comments

Comments

@RicCapUnitn
Copy link
Collaborator

When mem_opt is set to False Django (or MongoDD??) store the last query in cache; this memory is not necessary (at least if you do not want to run the extraction several times in a row); We should clear this cache and restrict data extraction to a maximum number of times to avoid performance issues and memory overflow.

@ricCap
Copy link
Owner

ricCap commented Oct 26, 2017

Actually this is not a problem and the query_mem_opt = False runs faster

@ricCap
Copy link
Owner

ricCap commented Dec 4, 2017

Cache is freed automatically by the system when requested. If the system has enough memory to cache query results it does, leaving at least 1GB of RAM always untouched.

@ricCap ricCap closed this as completed Dec 4, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants