Not sure if anyone has produced exact numbers but my experience is that number of rpc calls (get, put, etc) and number of distinct entities involved in each has generally more effect on "CPU hours cost" than the amount of data in any given entity being acted upon. So if you can reduce your # of rpcs by aggregating data in some way that may also reduce the $ cost dramatically.
I am not sure if app engine team intended for cost to be measured in this way but that seems to be the current model. On Sep 22, 6:16 pm, Rodrigo Moraes <[email protected]> wrote: > On Tue, Sep 22, 2009 at 7:11 PM, blscott wrote: > > > I have three tables consisting of 21 fields. The majority of them are > > strings and the maximum string length is approximately 50 chars. I > > had some 500's during the development, but not many overall. > > > Other than disabling autogenerate in the index.yaml, how would I take > > control of which fields are indexed? When I tried to set indexing on > > single fields I got an error that this was done automatically. > > > Thank you for your help. > > When definining Model properties, you can pass indexed=False as > parameter. Some properties are not indexed by default (Blob, Text). > > -- rodrigo --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
