CODEWITHSUNDEEP
google-app-enginegoogle-cloud-platform
tomsseisums
tomsseisums

Reputation: 13357

Is the service hourly pricing based on allocation or consumption?

Where with allocation I mean, that for how much time have I "assumed the ownership" of the resource.

And with consumption I mean, how much has the resource actually been used for.

For example, single vCPU:

Upvotes: 1

Views: 115

Answers (2)

Dan Cornilescu
Dan Cornilescu

Reputation: 39814

Standard and flexible environment pricing differ from each other by the granularity of billing:

  • a few instance classes in standard env vs a wider range of combinations of vCPU and memory units
  • some (small) differences in terms of uptime calculation and start/stop offsets

But fundamentally both charged based on consumption (as in uptime, not in effective CPU used!).

Scaling matters as well:

  • automatic and basic scaling shut down idle dynamic instances, more or less bringing the answer close to "consumption" for them.

  • manual scaling as well as resident instances in automatic/basic scaling are charged as "allocation" as they'll be always running

Upvotes: 1

John Hanley
John Hanley

Reputation: 81336

Billing is based on clock time, not percentage used during that time period.

If your usage of a compute resource is 0%, you will still pay for it (assuming that the compute resource is running and not shutdown).

Upvotes: 0

Related Questions