Is the service hourly pricing based on allocation or consumption?
up vote
1
down vote
favorite
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:
- My app engine works for a whole month, 24/7 =
30 * 24=720h. - Average CPU usage is
60%for the whole month. - Do I pay fixed price for
720h, or... - Do I pay calculated price for
720h * actual usage (60%)=432h?
google-app-engine google-cloud-platform asked Nov 7 at 21:36
jolt
7,5391764122
add a comment |
up vote
1
down vote
favorite
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:
- My app engine works for a whole month, 24/7 =
30 * 24=720h. - Average CPU usage is
60%for the whole month. - Do I pay fixed price for
720h, or... - Do I pay calculated price for
720h * actual usage (60%)=432h?
google-app-engine google-cloud-platform asked Nov 7 at 21:36
jolt
7,5391764122
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
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:
- My app engine works for a whole month, 24/7 =
30 * 24=720h. - Average CPU usage is
60%for the whole month. - Do I pay fixed price for
720h, or... - Do I pay calculated price for
720h * actual usage (60%)=432h?
google-app-engine google-cloud-platform asked Nov 7 at 21:36
jolt
7,5391764122
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:
- My app engine works for a whole month, 24/7 =
30 * 24=720h. - Average CPU usage is
60%for the whole month. - Do I pay fixed price for
720h, or... - Do I pay calculated price for
720h * actual usage (60%)=432h?
google-app-engine google-cloud-platform google-app-engine google-cloud-platform asked Nov 7 at 21:36
jolt
7,5391764122
asked Nov 7 at 21:36
jolt
7,5391764122
edited Nov 7 at 21:43
asked Nov 7 at 21:36
jolt
7,5391764122
asked Nov 7 at 21:36
jolt
7,5391764122
asked Nov 7 at 21:36
jolt
7,5391764122
7,5391764122
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
up vote
0
down vote
accepted
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).
answered Nov 7 at 22:01
John Hanley
11.2k2527
You know of any other cloud provider that bills based on actual usage?
– jolt
Nov 7 at 22:06
No I don't. I work with the major vendors (AWS, Azure, Google, IBM, Alibaba). Their pricing is based on clock time. Since your use case does not consume one App Engine resource entirely, I am not covering autoscaling, load balancing, etc where you can get economy of scale for larger compute infrastructures. Keep in mind that most of your billing will be storage costs and bandwidth. These items are usually larger than compute charges. For the cloud vendors the money is not so much in compute resources but storage and bandwidth charges.
– John Hanley
Nov 7 at 22:15
add a comment |
up vote
1
down vote
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
answered Nov 7 at 22:06
Dan Cornilescu
26.9k113161
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
accepted
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).
answered Nov 7 at 22:01
John Hanley
11.2k2527
You know of any other cloud provider that bills based on actual usage?
– jolt
Nov 7 at 22:06
No I don't. I work with the major vendors (AWS, Azure, Google, IBM, Alibaba). Their pricing is based on clock time. Since your use case does not consume one App Engine resource entirely, I am not covering autoscaling, load balancing, etc where you can get economy of scale for larger compute infrastructures. Keep in mind that most of your billing will be storage costs and bandwidth. These items are usually larger than compute charges. For the cloud vendors the money is not so much in compute resources but storage and bandwidth charges.
– John Hanley
Nov 7 at 22:15
add a comment |
up vote
0
down vote
accepted
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).
answered Nov 7 at 22:01
John Hanley
11.2k2527
You know of any other cloud provider that bills based on actual usage?
– jolt
Nov 7 at 22:06
No I don't. I work with the major vendors (AWS, Azure, Google, IBM, Alibaba). Their pricing is based on clock time. Since your use case does not consume one App Engine resource entirely, I am not covering autoscaling, load balancing, etc where you can get economy of scale for larger compute infrastructures. Keep in mind that most of your billing will be storage costs and bandwidth. These items are usually larger than compute charges. For the cloud vendors the money is not so much in compute resources but storage and bandwidth charges.
– John Hanley
Nov 7 at 22:15
add a comment |
up vote
0
down vote
accepted
up vote
0
down vote
accepted
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).
answered Nov 7 at 22:01
John Hanley
11.2k2527
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).
answered Nov 7 at 22:01
John Hanley
11.2k2527
answered Nov 7 at 22:01
John Hanley
11.2k2527
answered Nov 7 at 22:01
John Hanley
11.2k2527
answered Nov 7 at 22:01
John Hanley
11.2k2527
11.2k2527
You know of any other cloud provider that bills based on actual usage?
– jolt
Nov 7 at 22:06
No I don't. I work with the major vendors (AWS, Azure, Google, IBM, Alibaba). Their pricing is based on clock time. Since your use case does not consume one App Engine resource entirely, I am not covering autoscaling, load balancing, etc where you can get economy of scale for larger compute infrastructures. Keep in mind that most of your billing will be storage costs and bandwidth. These items are usually larger than compute charges. For the cloud vendors the money is not so much in compute resources but storage and bandwidth charges.
– John Hanley
Nov 7 at 22:15
add a comment |
You know of any other cloud provider that bills based on actual usage?
– jolt
Nov 7 at 22:06
No I don't. I work with the major vendors (AWS, Azure, Google, IBM, Alibaba). Their pricing is based on clock time. Since your use case does not consume one App Engine resource entirely, I am not covering autoscaling, load balancing, etc where you can get economy of scale for larger compute infrastructures. Keep in mind that most of your billing will be storage costs and bandwidth. These items are usually larger than compute charges. For the cloud vendors the money is not so much in compute resources but storage and bandwidth charges.
– John Hanley
Nov 7 at 22:15
You know of any other cloud provider that bills based on actual usage?
– jolt
Nov 7 at 22:06
You know of any other cloud provider that bills based on actual usage?
– jolt
Nov 7 at 22:06
No I don't. I work with the major vendors (AWS, Azure, Google, IBM, Alibaba). Their pricing is based on clock time. Since your use case does not consume one App Engine resource entirely, I am not covering autoscaling, load balancing, etc where you can get economy of scale for larger compute infrastructures. Keep in mind that most of your billing will be storage costs and bandwidth. These items are usually larger than compute charges. For the cloud vendors the money is not so much in compute resources but storage and bandwidth charges.
– John Hanley
Nov 7 at 22:15
No I don't. I work with the major vendors (AWS, Azure, Google, IBM, Alibaba). Their pricing is based on clock time. Since your use case does not consume one App Engine resource entirely, I am not covering autoscaling, load balancing, etc where you can get economy of scale for larger compute infrastructures. Keep in mind that most of your billing will be storage costs and bandwidth. These items are usually larger than compute charges. For the cloud vendors the money is not so much in compute resources but storage and bandwidth charges.
– John Hanley
Nov 7 at 22:15
add a comment |
up vote
1
down vote
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
answered Nov 7 at 22:06
Dan Cornilescu
26.9k113161
add a comment |
up vote
1
down vote
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
answered Nov 7 at 22:06
Dan Cornilescu
26.9k113161
add a comment |
up vote
1
down vote
up vote
1
down vote
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
answered Nov 7 at 22:06
Dan Cornilescu
26.9k113161
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
answered Nov 7 at 22:06
Dan Cornilescu
26.9k113161
answered Nov 7 at 22:06
Dan Cornilescu
26.9k113161
answered Nov 7 at 22:06
Dan Cornilescu
26.9k113161
answered Nov 7 at 22:06
Dan Cornilescu
26.9k113161
26.9k113161
add a comment |
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53198198%2fis-the-service-hourly-pricing-based-on-allocation-or-consumption%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
