Weekend stress testing with SQLite in multi-tenant

[lairtonmendes]

Hi everyone, just wanted to share some stress tests I ran over the weekend. I wanted to see with my own eyes that it wasn’t crazy to use SQLite in production (sorry @flavorjones but I couldn’t resist playing with this on my free time 😅).

The test setup was pretty simple:

• Created 1,000 tenants
• Each tenant had a table with 100,000 rows
• Exposed an endpoint to query a random row from a random tenant (the idea was to see how it behaves when multiple requests hit different tenants at the same time).

The results were surprisingly good: on an old computer I had lying around, running Omarchy without much fine tuning, I was able to easily reach 400 requests per second, with avg ~10ms and p95 ~15ms.

So yes — we’re going to use this at work. We’re designing an app that should serve more than 1,000 clients. We also have another large database with several TB of data, and the plan is to split it so each client only has access to their own slice.

And last but not least: thank you @flavorjones 🙏 you’re making my life a lot easier!

[flavorjones]

Nice! Thanks for sharing your results. 👏👏👏

I benchmarked (on my underpowered laptop) ~400 write requests per second. In another test on a beefier desktop machine, we were able to squeeze ~800 write requests per second out of the app!