Skip to content
Browse files
Docs - roll-up tip (#11677)
* Update

Added SE tip around roll-up.

* Update docs/ingestion/

Co-authored-by: Charles Smith <>

Co-authored-by: Charles Smith <>
  • Loading branch information
petermarshallio and techdocsmith committed Dec 7, 2021
1 parent d7463c9 commit c209db3a1de153604d33c3f8afdcdf38b454573a
Showing 1 changed file with 8 additions and 0 deletions.
@@ -30,6 +30,14 @@ At ingestion time, you control rollup with the `rollup` setting in the [`granula

When you disable rollup, Druid loads each row as-is without doing any form of pre-aggregation. This mode is similar to databases that do not support a rollup feature. Set `rollup` to `false` if you want Druid to store each record as-is, without any rollup summarization.

Use roll-up when creating a table datasource if both:
- You want optimal performance or you have strict space constraints.
- You don't need raw values from [high-cardinality dimensions](
Conversely, disable roll-up if either:
- You need results for individual rows.
- You need to execute `GROUP BY` or `WHERE` queries on _any_ column.
If you have conflicting needs for different use cases, you can create multiple tables with different roll-up configurations on each table.

## Maximizing rollup ratio

To measure the rollup ratio of a datasource compare the number of rows in Druid (`COUNT`) with the number of ingested events. For example, run a [Druid SQL](../querying/ query where "count" refers to a `count`-type metric generated at ingestion time as follows:

0 comments on commit c209db3

Please sign in to comment.