Skip to content

OPEN QUESTION: How to handle bloat in sqlite database? #11

Description

@plumocracy

Right now we don't prune the sqlite database very agressively. I want the user to be able to search historically (i think?) so we want some historical data but we dont want gigabytes and gigabytes of embedding data. The question then is this: How do we keep historical data without compromising quality or bloating the sqlite db?

  1. Compression maybe? : compress old data and only read it when it's needed?

I'm really unsure here.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions