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

index.sqlite is too large #2917

Open
2 of 3 tasks
linnnff opened this issue Nov 14, 2024 · 1 comment
Open
2 of 3 tasks

index.sqlite is too large #2917

linnnff opened this issue Nov 14, 2024 · 1 comment
Assignees
Labels
area:indexing Relates to embedding and indexing kind:bug Indicates an unexpected problem or unintended behavior "needs-triage"

Comments

@linnnff
Copy link

linnnff commented Nov 14, 2024

Before submitting your bug report

Relevant environment info

- OS:
- Continue version:
- IDE version:
- Model:
- config.json:

Description

index.sqlite is too large ,taking up 50GB of my space in C drive.

To reproduce

No response

Log output

No response

@sestinj sestinj self-assigned this Nov 14, 2024
@dosubot dosubot bot added area:indexing Relates to embedding and indexing kind:bug Indicates an unexpected problem or unintended behavior labels Nov 14, 2024
@sestinj
Copy link
Contributor

sestinj commented Nov 14, 2024

@linnnff have you been using Continue for a long time, with a large codebase, or trying a lot of different embeddings models? I'm trying to better understand which factors are contributing to this.

We store embeddings once for each repo and embeddings provider, unless there's some kind of leak

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:indexing Relates to embedding and indexing kind:bug Indicates an unexpected problem or unintended behavior "needs-triage"
Projects
None yet
Development

No branches or pull requests

2 participants