DuckDB inside OLTP databases

Plain DuckDB

Versions

Run asImageServerDuckDBDigest
DuckDB 1.4.3dbench/duckdb:1.4.3DuckDB 1.4.31.4.3sha256:ddf68226fc6361bcd0fdf4dde5d9d28ab686f9a9088dd2fb94a31611baa935ed
DuckDB 1.5.2-dev736dbench/duckdb:1.5.2-dev736DuckDB 1.5.2-dev7361.5.2-dev736sha256:efb098aaee0cd53609beef05736a7ca12adccba95d809269db9c7db3ec06c16b
DuckDB 1.5.3dbench/duckdb:1.5.3DuckDB 1.5.31.5.3sha256:697dc58e59ee554c9943c43367e0d03b562571019c1bb642727285f07ef35394
DuckDB 1.5.5dbench/duckdb:1.5.5DuckDB 1.5.51.5.5sha256:fa9ddda0848b69773a2bf83efd4762061d19d422d1b609d4c710ab38cbb37c06
DuckDB 2.0.0dbench/duckdb:2.0.0DuckDB 2.0.02.0.0sha256:f2528d483b1fc8b08b446e6cb88f5f0e4eb13b74d305bdc4c12320553df57131

Observed in this run

Generated the same way for every system from its result files: record counts per measure and status, and the reasons given for anything that is not ok.

DuckDB 1.4.3

DuckDB 1.5.2-dev736

DuckDB 1.5.3

DuckDB 1.5.5

DuckDB 2.0.0

Settings that differ from the defaults

No settings files for this system.

README

Plain DuckDB reference

DuckDB behind a small TCP JSON-lines query server (server.py), so query timing is measured server-side and excludes client startup. One cursor per TCP connection on the database file /var/lib/duckdb/tpch.duckdb.

Images (dbench/duckdb:<version>):

docker build -t dbench/duckdb:1.4.3 --build-arg DUCKDB_VERSION=1.4.3 systems/duckdb
docker build -t dbench/duckdb:1.5.5 --build-arg DUCKDB_VERSION=1.5.5 systems/duckdb
docker build -t dbench/duckdb:2.0.0 --build-arg DUCKDB_VERSION=2.0.0 systems/duckdb
# AliSQL snapshot (duckdb/duckdb commit 8a66223), built from source, version v1.5.2-dev736
docker build -t dbench/duckdb:1.5.2-dev736 \
  --build-arg DUCKDB_VERSION=1.5.2-dev736 \
  --build-arg DUCKDB_SOURCE_COMMIT=8a66223119b16000f3814fa7150cfa7370b63209 \
  --build-arg DUCKDB_PYTHON_TAG=v1.5.2 \
  --build-arg DUCKDB_GIT_DESCRIBE=v1.5.1-736-g8a6622311 systems/duckdb

Settings (from the container limits): threads = cores in the DB cpuset, memory_limit = 80% of the container memory (headroom for non-buffer allocations).

Schema: TPC-H tables with primary keys, no other indexes. There is no row store, so M11 and M12 are n/a.