From 3312fb810faf8fc90fd1de08806144e82fb31321 Mon Sep 17 00:00:00 2001 From: Trey Spiller <1831878+treysp@users.noreply.github.com> Date: Mon, 6 Jan 2025 15:38:01 -0600 Subject: [PATCH] Docs: cloud costs savings edits (#3564) --- docs/cloud/features/costs_savings.md | 32 +++++++++++++++++----------- 1 file changed, 20 insertions(+), 12 deletions(-) diff --git a/docs/cloud/features/costs_savings.md b/docs/cloud/features/costs_savings.md index 600cd4849..d4e77fc8d 100644 --- a/docs/cloud/features/costs_savings.md +++ b/docs/cloud/features/costs_savings.md @@ -1,17 +1,25 @@ # Data Warehouse Costs and Savings with Tobiko -Tobiko Cloud tracks data warehouse cost estimates per model for BigQuery and Snowflake projects. It will also estimate cost savings achieved by SQLMesh intelligently detecting when a model doesn’t need to be rerun. +Cloud data warehouses can be expensive, and finance departments are paying attention. When they come asking about your cloud budget, the best preparation is a granular understanding of how your project's components correspond to those costs. -If you'd like to see cost and savings estimates in Cloud and use a supported pricing plan, Tobiko can estimate your data warehouse costs for you and display them in various places on Tobiko Cloud. +Cloud warehouse costs are determined by how much computation occurs. Clouds report computation/cost for each executed query, but it is challenging to align every query with a specific model in your project. + +Tobiko Cloud solves this problem for you. It tracks data warehouse cost estimates per model for BigQuery and Snowflake projects that use a supported pricing plan. + +This granular cost information allows you to directly explain/justify your cloud warehouse expenditures. It also uncovers the models that could most benefit from efficiency improvements. + +Beyond tracking your warehouse costs, Tobiko Cloud estimates how much money it saved you! Its advanced column-level impact analysis saves you even more money than open-source SQLMesh. ## Supported Data Warehouse Pricing Plans -- BigQuery On Demand -- Snowflake Credits +Tobiko Cloud supports these cloud pricing plans: + +- BigQuery [On Demand](https://cloud.google.com/bigquery/pricing#on_demand_pricing) +- Snowflake [Credits](https://docs.snowflake.com/en/user-guide/cost-understanding-compute#label-what-are-credits) ## Data Warehouse Cost Configuration -If you use one of the supported pricing plans, in order to configure Tobiko Cloud to show cost information you will need to visit Settings. +Configure Tobiko Cloud to show cost information by navigating to the Settings page. ![Image highlighting location of the Settings link in the left site navigation](./costs_savings/costs-navigation.png) @@ -21,22 +29,22 @@ On the General settings page (1), select your pricing plan (2), enter your costs ## Where to find cost and savings estimates information -Estimated costs and savings are displayed on the homepage, production environment page, runs and plans pages, and individual model pages. +Estimated costs and savings are displayed on the Tobiko Cloud homepage, production environment page, runs and plans pages, and individual model pages. -Cost information on each page will look similar to the following: +Cost information on each page will look similar to: ![Example of costs and savings data as seen on the Tobiko Cloud homepage](./costs_savings/costs-example.png) -### Savings Categories +## Savings Categories -When calculating your data warehouse costs, we will calculate the amount you saved by using Tobiko as well! Tobiko Cloud also comes with additional change categorization capabilities, such as advanced column-level impact analysis. +When calculating your data warehouse costs, Tobiko Cloud also estimates how much money it saved you! Cost savings are broken up into three main categories: -- **Prevented Reruns**: If SQLMesh has already run an execution for a change in one environment, we won't need to rerun it in another environment (such as when a model change is backfilled on a development environment and then applied to prod) +- **Prevented Reruns**: If SQLMesh has already run an execution for a change in one environment, we won't need to rerun it in another environment (such as when a model change is backfilled on a development environment and then applied to prod). - **Unaffected Downstream**: Because SQLMesh understands SQL, we know if a downstream model is not affected by an upstream change and can avoid re-execution. - **Virtual Environments**: Using the Virtual data environments feature means new environments can be created without backfilling models within the new environment. -## Where to find cost savings information +### Where to find cost savings information -Most of the places where costs are displayed, cost savings will be shown as well. You can find how much you've saved using Tobiko by viewing the homepage, production environment page, and individual model pages. +Cost savings are shown in most of the places data warehouse costs are displayed. You can find how much Tobiko has saved you by viewing the homepage, production environment page, or individual model pages.