Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: docs for dwh cost estimates and savings #3554

Open
wants to merge 7 commits into
base: main
Choose a base branch
from

Conversation

caiters
Copy link
Contributor

@caiters caiters commented Dec 21, 2024

No description provided.


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)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It feels the virtual environments bullet is describing this same functionality

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the two are indeed similar so it makes sense that it feels the same, but maybe there's a better way to differentiate? - I can double check with @crericha that this language is correct

Copy link
Contributor

@treysp treysp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you! Made a PR against this branch so you can see my edits. #3564

@treysp treysp force-pushed the docs/costs-savings branch from 3312fb8 to ee8a5b8 Compare January 6, 2025 21:39
docs/cloud/features/costs_savings.md Outdated Show resolved Hide resolved
docs/cloud/features/costs_savings.md Outdated Show resolved Hide resolved

![Image highlighting location of the Settings link in the left site navigation](./costs_savings/costs-navigation.png)

On the General settings page (1), select your pricing plan (2), enter your costs, and then save (3).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What are default pricing plans? Include configs in writing or screenshots for those

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think I need a little clarification on this one - are you asking what the default values are for the pricing plans, or just what the form looks like? I could update the costs-steps.png file to include the full form with either bigquery or snowflake selected that would show the "cost per TB" or "cost per credit" field as well, or is there something else you are looking for?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"full form with either bigquery or snowflake selected that would show the "cost per TB" or "cost per credit" field as well"

Can you include screenshots of both and explicitly write out the defaults? Ex: BigQuery charges $6.25 per TB processed

image

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this along the lines of what you were thinking?

image

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I worry the code and documentation will get out of sync. It will be hard to remember the docs need to be updated if the defaults change.

docs/cloud/features/costs_savings.md Show resolved Hide resolved
docs/cloud/features/costs_savings.md Outdated Show resolved Hide resolved
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants