Plenty of these SQLite web front ends exist, including more enticing single static binaries in go, and they are always far too slow to use in anything but toy projects.
Should be standard to bench against a standard SQLite integration (on modern cpu with nvme).
Even PocketBase, for as nice as the UI is, an order of magnitude slower than SQLite directly.
Here's some rough numbers I've found using SELECT * FROM user LIMIT 1; per second ( 1x / 10x / 100x )
Plenty of these SQLite web front ends exist, including more enticing single static binaries in go, and they are always far too slow to use in anything but toy projects.
Should be standard to bench against a standard SQLite integration (on modern cpu with nvme).
Even PocketBase, for as nice as the UI is, an order of magnitude slower than SQLite directly.
Here's some rough numbers I've found using SELECT * FROM user LIMIT 1; per second ( 1x / 10x / 100x )
SQLite
68,000 / 50,000 / 4,000
SQLite WAL2 (3x Database files)
67,000 / 52,000 / 8,000
Pocketbase (CURL)
15,000 / 2,300 / 234
Pocketbase (Direct)
62,000 / 29,000 / 3,900
ws4sqlite (CURL)
20,000 / 2,600 / 255