What makes a time series oriented database (ex: QuestDB) more efficient for OLAP on time series than an OLAP "only" oriented database (ex: DuckDB) technically?

• materialize

  117 5,558 10.0 Rust

  The data warehouse for operational workloads. (by MaterializeInc)

  

AFAIK there is a lot of overlap between OLAP databases and time series databases. Timescale](https://legacy-docs.timescale.com/v1.7/introduction/architecture) gains a lot of its performance via the "Hypertable" abstraction which is fairly similar to something like Parquet partitioning/bucketing. In terms of performance I don't know if there is a huge gap either for non optimized use cases. The [Clickhouse] team for example feels confident that Clickhouse can be used as a time series database. There are also [independent benchmarks showing the performance is comparable[(https://pradeepchhetri.xyz/clickhousevstimescaledb/). I think where time series specific databases excel are in their tooling for time series specific queries. Things like continuous aggregates or efficient gap filling. But non time series databases are catching up on that front. Clickhouse has live views and Materialize is also playing in that space

• InfluxDB

  www.influxdata.com sponsored

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

Suggest a related project