Flexsave for Google Cloud
DoiT no longer offers Flexsave for Google Cloud. Please take a moment to review the Flexsave for Google Cloud Sunset FAQ that we have prepared to address the most common questions you might have.
DoiT Flexsave™ helps businesses manage and optimize their on-demand Google Cloud compute savings. It helps to ensure that on-demand compute workloads can be covered by resource commitments and delivers the equivalent savings of 1-year resource-based committed use discounts — without the commitment.
Capabilities
Flexsave monitors the utilization of your on-demand resources and adjust the mix of resource-based committed use discounts (CUDs) attached to your Google Cloud Billing account to maximize your potential savings.
Commitment types
Flexsave supports the following commitment types in all GCP regions:
General purpose E2, N2D, and Tau T2D commitments
General purpose N2 commitments (excluding sole-tenant nodes)
General purpose N1 commitments (excluding sole-tenant nodes, local SSD, and GPUs)
Memory-optimized M1 commitments
Compute-optimized C2, C2D commitments
Flexsave doesn't support the following commitment types:
Accelerator-optimized A2 commitments
Flexsave provides CUDs for GKE nodes that use the Compute Engine pricing model, but not CUDs for GKE Autopilot Mode.
Sustained use discounts (SUDs)
Google Cloud Compute Engine automatically applies sustained use discounts (SUDs) on resources that are used for more than a fourth of a billing month and are not receiving any other discounts. The discount increases incrementally with your usage.
To take full advantage of Flexsave without losing the benefit of SUDs, we recommend that:
If you use general-purpose N1 and memory-optimized M1 machine types, activate Flexsave no later than the second week of the month.
If you use general-purpose N2/N2D and compute-optimized C2/C2D machine types, activate Flexsave no later than the third week of the month.
FAQ
Can I use Flexsave with discount sharing disabled?
Unfortunately, no. Flexsave requires you to enable committed use discount sharing.
What changes should I expect in Google Cloud Console?
You should see:
Commitment scope set to Billing account
Projects with 3-year committed use discounts and IDs like
doitintl-fs-xxxxxxattached to your billing account
When enabling the billing account scope, the commitments will apply CUDs across all eligible usage (all projects) associated with this billing account.
See Flexsave projects/accounts for an example of how to view Flexsave projects/accounts in a Cloud Analytics report.
I just enabled Flexsave. Why do I immediately see charges for the CUDs you added to my account? Where are my credits?
When Flexsave adds CUDs to your Google Billing Account and discount sharing is enabled, your billing will immediately start to report the associated commitment charges.
However, whenever you enable discount sharing, the changes will only take effect the following day at midnight Pacific Standard Time (PST). After this short delay, your billing will start to report the associated commitment credits.
Why do I see discrepancies between charges and credits for my CUDs?
Google Cloud Billing experiences data latency for CUDs when discount sharing is enabled:
Cloud Billing data for commitment charges, committed use discount credits, and sustained use discount credits can be delayed for up to one-and-a-half days. This difference in timing can cause your most recent costs from the current and previous day to appear higher than expected because the credits to offset those costs are not yet attributed.
How soon after enabling Flexsave should I see the savings?
Flexsave monitors your resource utilization and leverages committed use discount recommendations from Google.
If you sign up for Flexsave as a SaaS customer, you should expect to see savings within 5 business days after enabling it.
It takes up to 2 business days to decide on the optimal coverage. Once Flexsave starts to add CUDs to your Google Billing Account, you'll see the savings within 72 hours.
If DoiT is your Google Cloud reseller, you should expect to see savings within 37 days after onboarding.
We start collecting your billing data after you complete the onboarding process. We need data from the last 30 days to formulate your plan (you can Import historical data to facilitate this process if applicable). Then it takes up to 7 days for the savings to show up in the DoiT Console.
Why aren't my savings showing up?
Savings always show with a three-day delay. For example, if today was the 23rd day of the month, your savings will be accurate to the 20th. At the beginning of a new month, the savings will show on the 4th day of the month.
What is the CUD analysis report?
The CUD analysis reports are offered by Google Cloud Billing to help you visualize and understand the effectiveness and financial impact of the purchased Committed use discounts (CUDs).
For example, you can use the CUD analysis report to show the coverage rate for all the Google Compute Engine (GCE) resources eligible for CUDs. A value of 0% means that a specific resource has no coverage at all, and a value of 100% means the resource is fully covered.
Can I still buy my own CUDs and flexible CUD from Google?
Yes, you can. Flexsave works exclusively with your on-demand compute usage and excludes anything already covered by your own commitments.
CUDs are applied in the following order to optimize their use:
- your own resource-based CUDs
- your own flexible CUDs
- DoiT Flexsave CUDs
Resources that are not covered by any discounts are eligible for sustained use discounts (SUDs).