Wow, that is all super low level internal stuff :-). I can tell you that the new fields are only populated for Commit(Txn) and that for all other calls the only cost that is not know ahead of time is IndexWrites (which I believe is usually ~2 * # of properties changed * # of indexes properties appear in). Hopefully the new pricing model is clear enough that you don't feel inclined to dig that deep.
On Sun, Jun 26, 2011 at 12:37 PM, Stephen <[email protected]> wrote: > On Sun, Jun 26, 2011 at 5:02 PM, Alfred Fuller > <[email protected]> wrote: > > > > - Additional small op charge per key fetched otherwise they function > identically. > > Speaking of charges, how are we to interpret the new fields > CommitCost.requested_entity_puts and > CommitCost.requested_entity_deletes in eg. the PutResponse protocol > buffer which were added in the latest SDK? Should we ignore the > existing IndexWrites, EntityWrites etc.? > > -- > 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.
