You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/pages/product/caching/using-pre-aggregations.mdx
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -601,6 +601,12 @@ The data for `zip_code_index` would look as follows:
601
601
| 88523 | 3800 |
602
602
| 88524 | 5000 |
603
603
604
+
### Compaction
605
+
606
+
Whenever a newer version of pre-aggregation is just built and becomes available its performance would be suboptimal as it's pending compaction.
607
+
Most of the essential compaction process usually takes several seconds to several minutes for bigger partitions after pre-aggregation creation, depending on the size of the partition and the Cube Store workers' processing power available.
608
+
This compaction process is usually unnoticeable for queries that are optimal in terms of index usage, so it's always best practice to make sure all of your queries match an index.
609
+
604
610
## Inspecting pre-aggregations
605
611
606
612
Cube Store partially supports the MySQL protocol. This allows you to execute
0 commit comments