adb performance & benchmarks

adb is built for petabyte-scale performance with sub-second latency. The benchmarks measure the parts of the system users feel most directly: how fast data uploads, how quickly a trace goes from ingested to visible, and how search holds up over large datasets.

​

What was measured

The benchmark suite covers five categories:

1. Dataset upload (programmatic): batch file ingestion via code.
2. Dataset upload (UI): the same upload through the user interface.
3. Trace upload (programmatic): ingesting individual trace events.
4. Real-time ingest-to-read: latency from an event arriving to it being visible in the UI.
5. Search over large data: full-text search across very large span datasets.

​

Methodology

Tests were run over a 150 MB/s down / 150 MB/s up connection. Full-text search was measured as regexp search over datasets of 5M and 10M spans, each span carrying a ~25 KB chat-text string. The adb (P50) column is the median database timing. Arize AX Platform is the end-to-end experience delivered to the user (database plus application). Platform A, Platform B, and Platform C are other observability platforms run through the same tests.

​

Results

​

What the numbers show

Across every category, adb’s raw database timings stay in the sub-second range even as row counts grow into the millions, and the end-to-end Arize AX platform stays fast where other platforms rate-limit, cap file sizes, drop records, or fail outright. The gap widens with scale: several platforms that keep pace on small trace batches become tens to hundreds of times slower, or stop working, as data volume climbs. adb keeps your traces, evaluations, and annotations in open Iceberg format, so Data Fabric can continuously sync that data straight to your own cloud warehouse, like BigQuery or Snowflake, for analytics and custom workflows.