From 49d94b3bc3bcd68546c9f81b36d2e81e8b2b24a5 Mon Sep 17 00:00:00 2001 From: lucia-vargas-a Date: Thu, 20 Jun 2024 12:59:13 +0200 Subject: [PATCH] Title --- src/cookbooks/data_modeling/using_aggregates.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/cookbooks/data_modeling/using_aggregates.md b/src/cookbooks/data_modeling/using_aggregates.md index aac92262a..67795caac 100644 --- a/src/cookbooks/data_modeling/using_aggregates.md +++ b/src/cookbooks/data_modeling/using_aggregates.md @@ -103,7 +103,7 @@ This doc is about when to use different options to aggregate data, their limitat - The aggregate uses a DISTINCT COUNT **and** the query matches exactly the Explore query. - The base table for the Explore is expected to change with added columns and Looker Explore will require modifications that also require re-creating the dashboards. When using aggregate awareness this re-create is **not** neccesary. -## What is the actual benefit? +## How to measure the benefit and savings? - Looker displays in the top right corner of a view or explore the amount of data that will be processed with and withouth using the aggregates. ![Looker cost saving](looker_cost_saving.png)