Tables

The first results are published in November 2026: ArcadeDB 26.11.1 against a multi-model subset of engines, measured on the November instrument. Until then MMDBBench shows its method and its lanes, and no numbers.

Most people arrive with tables, so this lane comes first. The tasks are TPC-C and TPC-H from the Transaction Processing Performance Council, the standard transaction and analytics workloads. TPC-C is many small reads and writes. TPC-H is a few large scanning queries.

Each engine answers the same question in its own query language: SQL where it has one, and its native language where it does not. The answers are hashed and compared before any time is published.

The lane will carry these tables:

• Online transaction processing: TPC-C's new-order and payment transactions on the TPC-H tables, and the single-record insert, read, update, and delete beside them. Each column is a warm median; the ninety-ninth percentile is printed for new-order, the transaction this table leads with. There is no cold column of its own because every operation runs against an already-open, already-warm database by construction.
• Online analytical processing: five analytical queries over the same documents. The cold column is the first query of a session on a database that has just been opened, and every other latency column is the warm median of the iterations that follow it.

The rules every result follows are in the methodology. The settings for each engine are on the engines page. If one is wrong, tell us.

• Graphs: Interactive and analytical queries on a social network graph.
• Vectors: Dense and sparse vector search, with recall beside every latency.
• Time series: Monitoring-style queries over timestamped readings.
• Cross-model: One operation across a vector, a graph edge, and a document.
• Lifecycle: Opening, closing, deployment boundaries, and what waiting for the disk costs.