For single machine workloads, it's probably still largely true. Though so sensitive to details that it's not a particularly useful benchmark. SQLite is often li

For single machine workloads, it's probably still largely true. Though so sensitive to details that it's not a particularly useful benchmark. SQLite is often literally unbelievably fast for many operations, and having it operating in the same process gives it a substantially lower minimum that separate dedicated processes can't compete with. But it's not really designed to do things asynchronously (e.g. no background optimizing while idle), or as-efficiently for very large (or strange) operations. Simpler caches and indexes, more straightforward behavior, etc.