4 ms·

SQLite benchmarks are deeply flawed. Somebody has proven that it can sustain 4M queries per second on bare metal, 1.5M qps on a cloud VM, and it happened over 7

SQLite benchmarks are deeply flawed. Somebody has proven that it can sustain 4M queries per second on bare metal, 1.5M qps on a cloud VM, and it happened over 7 years ago. Therefore I do not believe any number from SurrealDB. https://use.expensify.com/blog/scaling-sqlite-to-4m-qps-on-a-single-server https://use.expensify.com/blog/scaling-sqlite-to-4m-qps-on-a...

jarym 4mo ago
I concur. I had Claude try it out on a project I'm working on: Headline so far (nested, 10k, p50/p95/p99 µs): ┌─────────────────────┬─────────────┬────────────────┐ │ op │ SQLite │ SurrealKV │ ├─────────────────────┼─────────────┼────────────────┤ │ getattr │ 1.1/1.4/1.5 │ 65/92/120 │ ├─────────────────────┼─────────────┼────────────────┤ │ lookup │ 1.4/1.5/1.8 │ 73/102/138 │ ├─────────────────────┼─────────────┼────────────────┤ │ readdir_page │ 45/51/59 │ 1458/1678/1843 │ ├─────────────────────┼─────────────┼────────────────┤ │ create_child │ 34/55/74 │ 190/272/339 │ ├─────────────────────┼─────────────┼────────────────┤ │ record_write │ 8/14/19 │ 124/157/183 │ ├─────────────────────┼─────────────┼────────────────┤ │ apply_remote_object │ 9/12/17 │ 137/172/206 │ └─────────────────────┴─────────────┴────────────────┘ SQLite is ~15–60× faster on every op — and SurrealKV's reads are properly indexed, so this isn't a setup artifact.
declanrice 4mo ago
The repo is open source, so why not raise a PR to https://github.com/surrealdb/crud-bench https://github.com/surrealdb/crud-bench and point out any misconfigurations you find? It's good that they've made it open source, so can easily point out if there are any misconfiguration.

jarym 4mo ago

I concur. I had Claude try it out on a project I'm working on: Headline so far (nested, 10k, p50/p95/p99 µs): ┌─────────────────────┬─────────────┬────────────────┐ │ op │ SQLite │ SurrealKV │ ├─────────────────────┼─────────────┼────────────────┤ │ getattr │ 1.1/1.4/1.5 │ 65/92/120 │ ├─────────────────────┼─────────────┼────────────────┤ │ lookup │ 1.4/1.5/1.8 │ 73/102/138 │ ├─────────────────────┼─────────────┼────────────────┤ │ readdir_page │ 45/51/59 │ 1458/1678/1843 │ ├─────────────────────┼─────────────┼────────────────┤ │ create_child │ 34/55/74 │ 190/272/339 │ ├─────────────────────┼─────────────┼────────────────┤ │ record_write │ 8/14/19 │ 124/157/183 │ ├─────────────────────┼─────────────┼────────────────┤ │ apply_remote_object │ 9/12/17 │ 137/172/206 │ └─────────────────────┴─────────────┴────────────────┘ SQLite is ~15–60× faster on every op — and SurrealKV's reads are properly indexed, so this isn't a setup artifact.

declanrice 4mo ago

The repo is open source, so why not raise a PR to https://github.com/surrealdb/crud-bench https://github.com/surrealdb/crud-bench and point out any misconfigurations you find? It's good that they've made it open source, so can easily point out if there are any misconfiguration.