musql vs Turso

Two SQLite-compatible engines, both compiled to WebAssembly, each in its own Web Worker in this tab. Same data, same queries, same bound values. Every answer is cross-checked.

Your query

This session

Tables: t(id, sec, k, v, bid, payload) with an index on sec, and b(id, label), filled by one deterministic SQL statement in both engines. After loading, musql runs VACUUM, which lays the rows out in its columnar segments; Turso's VACUUM is experimental and off in its browser build, so it runs none. Times are measured in each worker around the engine's own JS API, so both include their binding. Race runs both workers at once, sharing your CPU; Duel runs one engine at a time, alternating who goes first, and scores the median.