Optimizing queries in InfluxDB 3 using progressive evaluation
Which SQL qualifies for ProgressiveEvalExec, how to see it in EXPLAIN, and how mixed overlapping files are still evaluated newest-first.
9 posts.
Which SQL qualifies for ProgressiveEvalExec, how to see it in EXPLAIN, and how mixed overlapping files are still evaluated newest-first.
How databases optimize queries — and how a ProgressiveEval operator made most-recent-value queries in InfluxDB 3 hundreds of times faster.
How to read a query plan in InfluxDB 3.0 — logical versus physical plans, EXPLAIN, and a leading-edge example.
Partitioning schemes supported by InfluxDB 3.0 and the trade-offs between large and small numbers of partitions.
The architecture of InfluxDB IOx (InfluxDB 3.0) — a cloud-scalable database for high-performance load and query on time series.
A hidden database server that handles post-ingestion and pre-query workloads so ingest and query do not share CPU and memory with compaction.
Deduplication as an alternative to transactions for eventually consistent use cases of a distributed database with defined primary keys.
How partitioning inside a shard adds pruning, intra-node parallelism, and fast deletion, and how to manage hot versus cold partitions.
Understand the two dimensions of scaling for database query and ingest workloads, and how sharding can make scaling elastic — or not.