TeaQL Was 2,000× Faster Than the Obvious SQLx Query—Here’s What Actually Happened
· 7 min read
We recently measured two implementations of the same application request over the MusicBrainz dataset:
Load the newest 100 recordings that have linked works, and load at most ten work relations for each recording.
The controlled SQLx test returned the same 100 recordings, 103 relation rows, 103 links, 103 link types, and Work-ID checksum through both paths. One took 5,871.169 milliseconds. The other took 2.469 milliseconds—a 2,378× difference inside SQLx itself.
TeaQL Rust previously completed the corresponding typed graph workload in 2.864 milliseconds. That does not mean TeaQL has a PostgreSQL driver 2,000× faster than SQLx. The difference was the amount of work requested from the database. The expert SQLx control proves it.