-
Notifications
You must be signed in to change notification settings - Fork 12.4k
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
Comments
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.. |
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.
The text was updated successfully, but these errors were encountered: