Hi Kenneth, check out Max's response from earlier, we are not charging for all the summarized by the Data Store API Calls that are currently listed in the dashboard but rather we will most likely be charging for entity reads, entity writes, and index writes. This is similar to what we are charging today but we are just charging the operation rather than CPU hours. Your cost for datastore operations should not go up by an order of magnitude. We are working on getting comparative bills out so that you can see what it will actually cost.
Hope that helps! Greg D'Alesandre Senior Product Manager, Google App Engine On Wed, May 11, 2011 at 9:48 AM, Kenneth <kennet...@aladdinschools.com>wrote: > Today I've got 557,464 Data Store API Calls so far. Under the new pricing > model that is going to cost me 50 cents assuming they're all single reads or > writes, which they're not. If I assume that the average is 10 entities, > which is certainly low, I'm actually looking at $5, or $50 if the average is > 100. I'm currently paying 30 cent for cpu in total today. Once again we're > back to an order of magnitude of difference just on the datastore calls, > maybe even two orders. > > Google, what are you thinking. > > -- > 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-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > 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 google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
