3 ms·
Define large. I'd guess sqlite can do 10-100K TPS, no problem. You'll want a read cache to avoid repeatedly rendering the same HTML, etc in the frontend, wher
by hedora 4y ago
Define large. I'd guess sqlite can do 10-100K TPS, no problem.
You'll want a read cache to avoid repeatedly rendering the same HTML, etc in the frontend, where most CPU is spent. That'll accidentally reduce database load.
Assuming 10% writes (which is really, really write heavy), that'll get you to 1M page views per second. After that, you'll need to rearchitect.
(MySQL and Postgres are probably better choices, but I'd evaluate all three if I was setting this up for real.)
- Closi 4y agoJust because you can use something doesn’t mean you should use it. If you have 10k writes a second and 90k reads a second then SQLite is an awful choice.
- kasey_junk 4y agoHave you benchmarked it? Given modern commodity servers and no network overhead I’d buy it not being a problem. My intuition is you are right but given the operational simplicity improvements it would be worth exploring.
- hedora 4y agoThis. Like I said, postgres or mysql are probably better choices. However, modern hardware (especially small sync disk writes) is really fast,and sqlite has its own strong points.