Is Cost Per Million Estimate Based On New Pricing?
114 views
Skip to first unread message
Bryce Cutt
Jan 23, 2012, 8:28:08 PM1/23/12
to Google App Engine, dra...@digerat.com
I am wondering if the cost per million estimate (reported in logs as
cpm_usd) is based on the new pricing model or is it still based on the
old pricing model?
Does anyone who is getting lots of hits have any numbers that show how
accurate of an estimate cpm_usd is?
cpm_usd) is based on the new pricing model or is it still based on the
old pricing model?
Does anyone who is getting lots of hits have any numbers that show how
accurate of an estimate cpm_usd is?
Richard Watson
Jan 23, 2012, 11:39:43 PM1/23/12
to google-a...@googlegroups.com, dra...@digerat.com
CPM = cost per mille, or thousand. That 1000-fold difference would cost you far more than multiple pricing changes!
Bryce Cutt
Jan 24, 2012, 12:31:04 AM1/24/12
to Google App Engine
My mistake. I really should RTFM.
Is the cost per thousand estimate based on the new pricing model or
the old one?
Is the cost per thousand estimate based on the new pricing model or
the old one?
Robert Kluin
Jan 26, 2012, 2:44:26 AM1/26/12
to google-a...@googlegroups.com
This is actually a very good question; I'd like to know the answer as well.
Robert
> --
> You received this message because you are subscribed to the Google Groups "Google App Engine" group.
> To post to this group, send email to google-a...@googlegroups.com.
> To unsubscribe from this group, send email to google-appengi...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
>
Ikai Lan (Google)
Jan 26, 2012, 6:13:40 PM1/26/12
to google-a...@googlegroups.com
Those should be based on the old pricing. The old pricing is based on CPU milliseconds. That number is less meaningful (not meaningful anymore?) because you are billed for instance hours, and you have concurrent requests. Datastore ops are also not included.
At some point we should get rid of those and surface the number of datastore ops + other costs. I'm not sure what the consequences are for outright removing that field, though, so it'll require some examination.
Bryce Cutt
Jan 27, 2012, 3:32:24 AM1/27/12
to Google App Engine
I would definitely be interested in a replacement that is based on the
new pricing.
Any suggestions on a good way to estimate costs using information that
is currently available?
On Jan 26, 3:13 pm, "Ikai Lan (Google)" <ika...@google.com> wrote:
> Those should be based on the old pricing. The old pricing is based on CPU
> milliseconds. That number is less meaningful (not meaningful anymore?)
> because you are billed for instance hours, and you have concurrent
> requests. Datastore ops are also not included.
>
> At some point we should get rid of those and surface the number of
> datastore ops + other costs. I'm not sure what the consequences are for
> outright removing that field, though, so it'll require some examination.
>
> --
> Ikai Lan
> Developer Programs Engineer, Google App Engine
> plus.ikailan.com
>
new pricing.
Any suggestions on a good way to estimate costs using information that
is currently available?
On Jan 26, 3:13 pm, "Ikai Lan (Google)" <ika...@google.com> wrote:
> Those should be based on the old pricing. The old pricing is based on CPU
> milliseconds. That number is less meaningful (not meaningful anymore?)
> because you are billed for instance hours, and you have concurrent
> requests. Datastore ops are also not included.
>
> At some point we should get rid of those and surface the number of
> datastore ops + other costs. I'm not sure what the consequences are for
> outright removing that field, though, so it'll require some examination.
>
> --
> Ikai Lan
> Developer Programs Engineer, Google App Engine
> plus.ikailan.com
>
> On Wed, Jan 25, 2012 at 11:44 PM, Robert Kluin <robert.kl...@gmail.com>wrote:
>
>
>
>
>
>
>
> > This is actually a very good question; I'd like to know the answer as well.
>
> > Robert
>
>
>
>
>
>
>
>
> > This is actually a very good question; I'd like to know the answer as well.
>
> > Robert
>
Ikai Lan (Google)
Jan 27, 2012, 4:43:34 PM1/27/12
to google-a...@googlegroups.com
I don't have any great ones. It's harder to estimate instance hours, but if you have a good sense of datastore ops, you'll at least be able to estimate this cost based on how frequently certain URIs are called. Two releases ago, we shipped a feature that lets you see number of datastore ops. I believe this is available in the local admin (/_ah/admin).
Bryce Cutt
Jan 27, 2012, 7:45:38 PM1/27/12
to Google App Engine
Thanks for the responses Ikai. I will work out some rough estimates
using read/write counts and handler runtimes/calls.
- Bryce
using read/write counts and handler runtimes/calls.
- Bryce
Reply all
Reply to author
Forward
0 new messages