Skip to content

Investigate memory usage and an on-disk index #352

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

Open
fwcd opened this issue Apr 23, 2022 · 1 comment
Open

Investigate memory usage and an on-disk index #352

fwcd opened this issue Apr 23, 2022 · 1 comment
Labels
code quality Refactoring, tests etc. index Related to the symbol indexer

Comments

@fwcd
Copy link
Owner

fwcd commented Apr 23, 2022

Even on small projects the language server frequently uses several gigabytes of memory, especially when there are lots of symbols to be indexed (note that this includes the entire dependency tree!).

Since we probably do not query the database so frequently that we need it to be in memory, perhaps we could look into using an on-disk database such as SQLite? (This would additionally have the advantage of not requiring a reindex every time the project is opened, which would be in line with #337)

@D1360-64RC14
Copy link

Yeah, it needs some optimization.
It's impossible to use the VSCode plugin on my modest machine (8 GB of RAM). Doing some tiny work on a main function fills 3 GB of RAM in minutes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
code quality Refactoring, tests etc. index Related to the symbol indexer
Projects
None yet
Development

No branches or pull requests

2 participants