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

Parsing of dependencies #121

Closed
felixfbecker opened this issue Oct 26, 2016 · 3 comments
Closed

Parsing of dependencies #121

felixfbecker opened this issue Oct 26, 2016 · 3 comments
Labels

Comments

@felixfbecker
Copy link
Owner

Currently the biggest part while indexing is indexing the dependencies. For example, this project has 78 files + 1560 files in dependencies. I was thinking about whether we can skip re-parsing of dependencies by inspecting composer.lock. For example, we could make a separate cache for each dependency and copy the composer.lock to the cache folder, then only reparse if the installed version changed. This would drastically reduce the index time and CPU usage.

@yarcowang
Copy link

Yes, I think so. Or maybe you can keep a copy of composer.lock and only re-parsing those changed dependencies packages.

@diffen
Copy link

diffen commented Oct 18, 2017

Is there any way to exclude certain files from LSP permanently? I found this issue via the CPU overloading issue on VSCode. It seems that the caching extension has been implemented but there is no .phpls folder anywhere on my Mac. So the files don't seem to be cached and the language server parsing seems to go on forever. In fact, I think it's an endless loop and the parsing never ends.

@felixfbecker
Copy link
Owner Author

This issue is outdated. Please open a new issue and check your logs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants