[google-cloud-sql-discuss] Re: Cloud SQL PostgreSQL Committed Use

I believe your understanding is correct, for an instance with 4 HA vCPUs committed resource shall be 8 vCPUs. Standby instance is always running in HA configuration and billed the same as master instance. Also the documentation doesn't mention any exclusions for HA setups. 

On Wednesday, January 13, 2021 at 8:30:37 AM UTC+1 rajat....@telusinternational.com wrote:

Hi, Thanks for the explanation. 

A few questions:

How is High Availability resource calculated. If there is a instance with 4 HA vCPUs, for it committed resource shall be 8 vCPUs? Or committed resource shall be 4 HA vCPUs only?
Is the commitment dependent on number of instances using the resources ?

On Saturday, 9 January, 2021 at 4:49:11 am UTC+5:30 sohailalvi wrote:

Hello,

For your particular use case scenario, you can scale up the resources but you will be charged at standard billing for the differences in the resource above the committed use discount resources . You cannot scale down or in other you cannot  change or modify your CUD after you purchase a commitment , even your resource utilization is under CUD but you will be charged based on standard Committed Use Discounts (CUDs).

In  order to understand the concept of CUD , please read the following documents:

1-  Committed use discounts [1].

2-  Analyze the effectiveness of your resource-based committed use discounts [2].

3-  VM instances pricing[3].

Committed Use Discounts (CUDs) allow any customer to receive a substantial discount by committing to use a minimum quantity of concurrent GCE resources and reservations for 1 year or 3 years. Reservations allow you to reserve certain GCE resources (vCPUs, memory, GPUs, PD and/or Local SSD) in a specific Zone for later consumption without the hassle of running and monitoring VMs to hold the desired capacity.

Committed use discounts are ideal for workloads with predictable resource needs. When you purchase a committed use contract, you purchase compute resources (vCPUs, memory, GPUs, and local SSDs) at a discounted price in return for committing to paying for those resources for 1 year or 3 years. The discount is up to 57% for most resources like machine types or GPUs. The discount is up to 70% for memory-optimized machine types.[1].

By default, committed use discounts apply at the project level, but you can enable discount sharing from your billing account to share discounts across multiple projects.

Note:

1- After you create a commitment, you can't cancel it. You must pay the agreed upon monthly amount for the duration of the commitment

2- After you purchase a commitment, you can't change it. If you need to modify a commitment, purchase a new commitment with a new expiration date for the incremental amount.

After purchasing, you are billed monthly for the resources you purchased for the duration of the term you selected, whether or not you use the services. If you have a predictable workload, you can use discounts to help you cut costs on resources that you need.

Committed use discounts work on most Compute Engine machine types, including predefined and custom machine types, however, f1-micro and g1-small shared-core machines are excluded. Committed use discounts are simple and flexible, and require no upfront costs. Discounts apply to the aggregate number of vCPUs, memory, GPUs and local SSDs within a region, so they are not affected by changes to your instance's machine setup.

For your particular use cases please read  the section " How committed use discounts work" [1] and you will know in detail.

For example, if you purchase a commitment for 8 cores, and you run 24 cores during the month, you will receive committed use discounts for 8 cores. The other 16 cores will be billed at standard, non-committed use rates. Keep in mind that after you purchase a set amount of commitments, you're billed for those commitments monthly, even if you don't use them. For example, if you purchase commitments for 8 cores, you're billed the committed use rates for those 8 cores for the whole month, even if you might have only run these cores for a part of the month. It is to your advantage to purchase commitments only in increments you know you will use.

You can scale up but will be charged at standard billing for the differences in the resource .

Thanks You,

Links:
[1] https://cloud.google.com/compute/docs/instances/signing-up-committed-use-discounts.

[2] https://cloud.google.com/billing/docs/how-to/cud-analysis-resource-based#understanding_commitment_recommendations.

[3] https://cloud.google.com/compute/vm-instance-pricing

On Friday, January 8, 2021 at 6:54:39 AM UTC-5 rajat....@telusinternational.com wrote:

Hi, 

can the configuration and number of instance be scaled up/down during committed use?

is there some billing difference in the cases below?:

If Committed Use is configured at 2 vCPUs and 10GB Memory

Also, Instance configuration is 1 HA vCPUs and 5GB HA Memory

or

If Committed Use is configured at 1 HA vCPUs and 5GB HA Memory

Also, Instance configuration is 1 HA vCPUs and 5GB HA Memory

or

If Committed Use is configured at 1 HA vCPUs and 5GB HA Memory

Also, Instance1 configuration is 1 vCPUs and 5GB Memory

Instance2 configuration is 1 vCPUs and 5GB Memory

or

If Committed Use is configured at 4 vCPUs and 10GB Memory

Also, Instance1 configuration is 3 vCPUs and 6GB Memory,

Instance2 configuration is 1 vCPUs and 4GB Memory

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/3b477c63-a212-48b4-b945-3610529af611n%40googlegroups.com.