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

Compilation server cache size #5754

Closed
ncannasse opened this issue Oct 14, 2016 · 1 comment
Closed

Compilation server cache size #5754

ncannasse opened this issue Oct 14, 2016 · 1 comment
Assignees
Milestone

Comments

@ncannasse
Copy link
Member

Usually there should be no need to clear the cache of the compilation server. However in case the user switch between many different projects and/or different defines (causing different cache contexts to be created) this could trigger a lot of memory to be allocated and never released.
#5735 is one particular example of that

What should be done would be for each cached module / context store a "LastUsed" timestamp, then when we grow to a certain threshold of memory (measurable with Gc.quick_stat and to be configurable with a define) we could discard the contexts and modules that have not been used for a long time.

For the modules it's a bit more complex since it requires to discard as well all the dependencies TO it (recursively).

@Simn Simn modified the milestone: 4.0 Jan 9, 2017
@Simn Simn removed this from the Release 4.0 milestone Apr 17, 2018
@Simn Simn added this to the Design milestone Apr 18, 2018
@ncannasse
Copy link
Member Author

With 64 bits this is no much longer an issue, closing for now.

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