8 ms versus 3.8 seconds
This result refers to one analytical database query run against the same data in an internal comparison. It is not an end‑to‑end application, auction, incident, or model response time.
This result refers to one analytical database query run against the same data in an internal comparison. It is not an end‑to‑end application, auction, incident, or model response time.
Performance varies with joins, grouping, selectivity, cardinality, schema irregularity, data temperature, and concurrency. Oliver is designed to perform especially well on difficult analytical shapes.
The CPU and GPU figures should not be read as one universal speedup. Hardware, memory, storage, caching, and deployment topology all materially affect the result.
Lower compute and storage use comes from columnar compression, elastic stateless cells, ingest‑time resolution, and avoiding repeated agent work. The contribution of each factor varies.