tursodatabase / tursodatabase/libsql
How big can be one database size?
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 17.2k
- Forks
- 531
- Avg merge
- 1h 12m
- Merged PRs (30d)
- 1
Description
I'm planning to introduce a Database in my (vercel edge) production app and want to know how big can the turso.tech database be. I don't want to have a single db-per-user approach. Is there an upper cap to the size? Are there any gotchas if I use single db like degraded performance after certain size?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are mentioned. Start by establishing the supported database size limit and any size-related performance caveats for libSQL/SQLite, then document those answers in the relevant project documentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sqlite
- Domain
- databases
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100