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

How and when do we process mumblings and build the vector database? #27

Open
Tracked by #26
kikuomax opened this issue Oct 9, 2023 · 5 comments
Open
Tracked by #26
Assignees
Milestone

Comments

@kikuomax
Copy link
Member

kikuomax commented Oct 9, 2023

No description provided.

@kikuomax kikuomax added this to the Sprint 6 milestone Oct 9, 2023
@kikuomax kikuomax self-assigned this Oct 9, 2023
@kikuomax
Copy link
Member Author

kikuomax commented Oct 9, 2023

How about to process mumblings and rebuild the database every day until the update capability is implemented?

@kikuomax
Copy link
Member Author

kikuomax commented Oct 9, 2023

Recalculating embeddings for all the mumblings every day is waste of money. So we want to cache the embeddings.

@kikuomax
Copy link
Member Author

kikuomax commented Oct 9, 2023

How do we configure parameters for database building:

  • Number of partitions?
  • Number of codes (clusters)?

@kikuomax
Copy link
Member Author

kikuomax commented Oct 12, 2023

The initial version may be published with a database built offline with the experimental project mumble-embedding.

@kikuomax
Copy link
Member Author

We want to index every mumbling when it is stored in the outbox folder.
We want to progressively update the vector database with the planned new feature of flechasdb:

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

No branches or pull requests

1 participant