Everything I've heard from the GAE team indicates that each index change would be a separate "datastore operation" - so if you write 100 entities with 3 indexes each, that's 300 operations.
I'm just curious to know if a delete is the same as a write - my impression (unscientific) is that deletes up to this point are considerably more expensive than writes. Maybe the flattening of operations will equalize that. Jeff On Thu, May 26, 2011 at 12:26 PM, Jason Collins <[email protected]> wrote: > Jeff, good point on the new pricing model. From what I understand, > we'd get charged on an API call (e.g., each call to db.delete()), > regardless of the number of indexes (which make up a good portion of > the overall CPU costs in our case). > > There likely is a fairly substantial difference (reduction) of cost > under the new model. > > j > > On May 26, 12:54 pm, Jeff Schnitzer <[email protected]> wrote: >> On Thu, May 26, 2011 at 10:58 AM, Calvin <[email protected]> wrote: >> > It would make a difference because you could do the deletions within the >> > daily free quota. >> >> It's probably fair to assume that his application is already billed >> way beyond the free quota. >> >> Deleting data does seem painfully slow and expensive. I wonder, does >> this change at all with the new pricing model? >> >> Jeff > > -- > 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.
