Correct answers
12 of 12 systems answered all 22 queries with the reference result.
A neutral comparison of database servers that embed DuckDB, against plain DuckDB at several versions and row-store baselines, on the same TPC-H data with the same container limits. There is no overall score and no ranking: read each measure with its failures and its n/a cells.
Marks on charts and tables: ✗ wrong result (never drawn as a bar), T/O timeout, E error, C crashed, ! failed to run, – n/a. Hover a mark for the reason.
Computed from the result records of this page, one sentence per measure, with every system in the same order. They state counts and ranges; they do not rank systems or give an overall verdict. Each finding links to the measure's charts.
12 of 12 systems answered all 22 queries with the reference result.
On the 22 queries every integration answered correctly, the total warm time was 5.30 s to 151 s across all 5 integrations, and 2.96 s to 4.07 s for plain DuckDB.
Against plain DuckDB at the same DuckDB version, the geometric-mean time ratio was 1.23x to 29.39x across all 5 integrations. 1x means no cost for running inside the server.
At 16 concurrent streams, throughput was 1,287 qph to 33,975 qph across all 8 systems measured.
120 SQL statements an OLTP application would send, checked against the server's own row-store tables. A wrong result is silent: the statement succeeds and the answer differs.
TPC-H queries seen on the row path: none on 5 of the 5 integrations that report it. Of the read probes, the share answered on the row path instead of in DuckDB was 0% to 86.7%.
Bulk load of the TPC-H data took 17.28 s to 1,523 s across all 10 systems.
4 of 4 systems answered all 22 queries with the reference result. On the 22 queries every entry point answered correctly, the total warm time was 7.39 s to 8.90 s across all 3 entry points, and 7.42 s for plain DuckDB.
Systems appear in the same order everywhere: database integrations A to Z, plain DuckDB, row-store baselines. Totals use only the queries every integration completed correctly, so everyone is scored on the same work. VillageSQL has no DuckDB table type, so its row here is n/a; its numbers are under Parquet entry points below.
Sum of warm medians over the queries that every integration ran correctly. Lower is better.
Concurrent TPC-H streams, warm cache. Higher is better.
Ratio to plain DuckDB at the same version; the headline uses the same queries for every system. Each system's own geomean and its coverage are in the table below.
| System | DuckDB | Total, common queries | Own total (ok/total) | Throughput, 16 streams (qph) | Overhead, common | Overhead, own geomean (ok/total) | Plain baseline used |
|---|---|---|---|---|---|---|---|
| AliSQL | 1.5.2-dev736 | 5.30 s | 5.30 s (22/22) | 17,407 | 1.23x | 1.23x (22/22) | |
| MariaDB | 1.5.5 | 5.49 s | 5.49 s (22/22) | 16,861 | 1.28x | 1.28x (22/22) | |
| Percona | 2.0.0 | 5.47 s | 5.47 s (22/22) | 19,594 | 1.64x | 1.64x (22/22) | |
| pg_duckdb | 1.4.3 | 151 s | 151 s (22/22) | 1,287 | 29.39x | 29.39x (22/22) | |
| pg_ducklake | 1.5.3 | 7.73 s | 7.73 s (22/22) | 11,521 | 2.04x | 2.04x (22/22) | |
| DuckDB 1.4.3 | v1.4.3 | 4.07 s | 4.07 s (22/22) | 22,476 | – | ||
| DuckDB 1.5.2-dev736 | v1.5.2-dev736 | 3.91 s | 3.91 s (22/22) | – | – | ||
| DuckDB 1.5.3 | v1.5.3 | 3.90 s | 3.90 s (22/22) | – | – | ||
| DuckDB 1.5.5 | v1.5.5 | 3.87 s | 3.87 s (22/22) | 23,449 | – | ||
| DuckDB 2.0.0 | v2.0.0 | 2.96 s | 2.96 s (22/22) | 33,975 | – | ||
| MySQL InnoDB | n/a | 1,036 s | 1,036 s (22/22) | – | – | ||
| PostgreSQL | n/a | 188 s | 188 s (22/22) | – | – | ||
| VillageSQL | 1.5.5 | – | – | – | measured on Parquet files only; see Parquet entry points |
A second workload on the same TPC-H data: DuckDB SQL over Parquet files, sent through each system's raw DuckDB
entry point (VillageSQL duckdb_query(), pg_duckdb duckdb.query(), MariaDB run_in_duckdb())
and plain DuckDB. These numbers are not comparable with the table-based ones above and are never drawn on the same chart.
Sum of warm medians over the queries every entry point ran correctly. Lower is better.
Details: explore the data, all charts, methodology and every setting.