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

Grace period strategy for unloading projects #35115

Open
DanielRosenwasser opened this issue Nov 14, 2019 · 1 comment
Open

Grace period strategy for unloading projects #35115

DanielRosenwasser opened this issue Nov 14, 2019 · 1 comment
Labels
Domain: Performance Reports of unusually slow behavior

Comments

@DanielRosenwasser
Copy link
Member

Today, navigating to a file in another project might involve a full project load. Bad! Users often navigate back to the original project, and then dive right back into the loaded project. Unfortunately, by the time that they do that, that project is unloaded and all the work has to be done all over again.

We might want to consider something like a "grace period" for unloading projects when the last open file of a project is closed.

@sheetalkamat
Copy link
Member

Currently grace period is till next file open (which makes the project orphan).. I had this idea of keeping projects alive based on references and usage and unload them when their cache sizes exceed certain point (eg. number of symbols, types, assignability , other caches we might consider good indication of size it would free up to take into account how many projects to unload as well) and then unload it.. Haven't had time to prototype and play around on that..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Domain: Performance Reports of unusually slow behavior
Projects
None yet
Development

No branches or pull requests

2 participants