Hey Jamie,
In Greg's FAQ post he explained what constituted a datastore
operations. Each entity and corresponding index written is an
operation, every entity read is an operation, query results read, and
indexes scans (though scans will apparently not be billed). I agree
that this could add up fast, particularly on writes -- time to make
sure all properties you don't query on are not indexed. We've yet to
hear if keys_only queries will be billed differently, though they are
faster and hence will be cheaper since you'll use less instance time
waiting.
https://groups.google.com/d/topic/google-appengine/ob-kMuDAAqc/discussion
I know you didn't want to hear this, but it really isn't that much
different than 'API CPU time'. You can do some tests to demonstrate
this, setup a simple handler to write an entity then add an index,
write, repeat a few times and check the API CPU used. I've not done
the math to verify, but I think you are right about this amounting to
a large quota reduction.
Robert
On Sun, Jun 5, 2011 at 10:24, JH <[email protected]> wrote:
> Hopefully somebody from Google can confirm this info soon?
>
> I have not participated in much of the "new price bashing" since the
> initial shock of
> day 1. However, to me this seems like one of the most restrictive
> pricing changes of all.
> If you count datastore operations by # of entities returned, these
> numbers seem *EXTREMELY*
> high to me.
>
> First of all, this will put the smallest of apps beyond the free app
> quota.
>
> Secondly, this could really add up for the paid apps. I don't want to
> see GAE priced out
> of popularity. I think it's very important to recognize part of GAE's
> appeal to this point
> has been it's afford-ability. I don't want Google to loose money on
> the product, but I really
> hope the lack of a response is due to Google changing their mind. If
> datastore operations equaled maybe
> 1 api call for reads, no matter how many entities returned, 50k free
> + .01 per 10k sounds affordable.
> The per entity pricing will add up fast. Don't tell me it's similar
> to what you do now. Maybe in theory it
> is but it is so drastically different from today's quotas I believe
> you are being very disingenuous
> to tell people this change is not that different.
>
> On May 11, 4:41 pm, Kenneth <[email protected]> wrote:
>> Hi Greg,
>>
>> Thanks for the answer. I'm just having trouble seeing what API calls are
>> not get and puts, are deletes not covered?
>>
>> Anyhow, I'm looking forward to seeing my comparative bill. :-)
>>
>> Thanks again,
>> Kenneth
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>
>
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en.
