One large table vs many small tables
Hi all!
I was wondering if anyone did any performance benchmarks between having many (100s) of small tables vs having a single large (millions of rows) table. If there are any articles on this I'd love to read, or if anyone has any insights or recommendations on the topic.
Thanks in advance!
3 Replies
Thanks for posting in <#1088161997662724167>.
Reminder: If you have a Convex Pro account, use the Convex Dashboard to file support tickets.
- Provide context: What are you trying to achieve, what is the end-user interaction, what are you seeing? (full error message, command output, etc.)
- Use search.convex.dev to search Docs, Stack, and Discord all at once.
- Additionally, you can post your questions in the Convex Community's <#1228095053885476985> channel to receive a response from AI.
- Avoid tagging staff unless specifically instructed.
Thank you!
Just one bit of info to consider, indexes generally provide the performance benefits of many small tables while maintaining the convenient data model of a larger table.
hi! it won't make much performance difference. everything is btrees all the day down, so accessing any given row is O(log n)
even your filesystem is a btree so by splitting things into multiple files, that's just... another btree 🙂
and that's even if hte database chooses to split your tables into seperate files, which many do not
so definitely just organize your tables whatever way makes your life easier, and don't worry too much about the performance