3 ms·
For my use case (small datasets), query execution feels instant. No perceptible lag between user action and result. Though I haven't done formal benchmarking. T
by quirissum 5mo ago
For my use case (small datasets), query execution feels instant. No perceptible lag between user action and result. Though I haven't done formal benchmarking.
The initial load time is the bottleneck, not query execution. Whether that's the transpiler or just the Go runtime overhead I can't say without proper benchmarking.
- ncruces 5mo agoThanks! Yeah, I guess on the web it would always manifest as load time. But order of magnitude, with everything cached, on a decent laptop/desktop, is it a few seconds, or a minute? Because what I get from testing in CI is every test takes a minute.
- quirissum 5mo agoWith everything cached in production (compressed) it takes ~100ms to load the binary. Total global initialization including Go runtime startup and SQLite connection takes ~280ms on an M1 MacBook Pro. So well under a second end to end with a warm cache.
- ncruces 5mo agoThat's good to know, thanks! It makes this quite realistic, which might mean a good/great OPFS VFS (like Roy's) actually starts to make sense. https://github.com/rhashimoto/wa-sqlite/discussions https://github.com/rhashimoto/wa-sqlite/discussions Unfortunately I'm not knowledgeable enough on the browser side of things to advance something like that, and have quite a bit on my plate already. But if there's interest I can help demystify the SQLite/VFS side of things. Feel free to (e.g.) open a GitHub discussion on my repo to track this.