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
Limit Extension storage usage #185
Comments
Wow, indeed, the workspaceStorage grows freakingly fast. My 13 workspaces eat up to 3.5GB :-/ This is caused by Eclipse JDT new Java index . There's nothing much we can do at that point about limiting its size, other than disabling it completely, which is not something I'm too keen on doing (i.e. exposing another eclipse internal). I'll ask the JDT team about it |
Larger index files vs speedier searches was a design decision. I do not think this is a performance problem though. |
So I commented on Eclipse Bugzilla. Turns out even disabling the index will not prevent the index.db creation. |
@rgrunber brings us hope with his work on JDT shared indexes: |
@rgrunber https://twitter.com/artursignell/status/1437817323574943748 reminded me of this issue. We should prioritize this work in the coming sprints |
I'm going to close this issue as it was originally filed against the |
Hi redhat.java 0.82.0 is taking several gigabytes of storage Storage contains big files like
Is this expected behavior? If so, could the extension be configured to
Thanks for your help |
@sguillia yes, that's what we're planning in #2110. I think the first part will be to create some setting option that clears out older workspace storage locations (eg. The second part would be to take advantage of some capabilities we have to share indexes across projects, where possible. |
From @Geeprox on April 13, 2017 9:39
There are so many index.db files that takes a lot of storage space
(for example: \AppData\Roaming\Code\User\workspaceStorage\13d502476c69532f0fce4f9ab9ea9f18\redhat.java\jdt_ws.metadata.plugins\org.eclipse.jdt.core\index.db)
I know they are useful caches, but can we give it a limit space or give it a survival time or something else?
Copied from original issue: microsoft/vscode#24666
The text was updated successfully, but these errors were encountered: