Once you have generated a cost-saving plan, how should you act on it to realize the savings?
If you audited your ad-hoc queries, you will need to materialize the common SQL in your warehouse as a table to realize the cost savings. By pre-calculating repeatedly accessed data, you can save significant amounts of compute.
Depending on the source of your ad-hoc queries, you can then:
- point your dashboards to use the new table, or
- point your users to use the new table (and provide them examples using our rewritten queries)
If you audited your pipeline queries, you must update an existing pipeline using the common SQL to realize the cost savings. You can generate the same data with fewer tables by updating one pipeline and deprecating the semantically equivalent pipelines.
Consolidating pipelines helps you save both compute (for processing the pipelines) and downstream storage (for storing the output of pipelines).
Updated 2 months ago