You are probably indexing all of the properties (this is default behavior). Indexes are expensive to create and consume a large amount of storage as well. The solution is simply not to index what you don't need to query on.
The mechanism to flag a property as unindexed varies with which GAE you are using (python vs java) and which libraries you use to access the datastore. It's all in the documentation. Jeff On Wed, Jun 15, 2011 at 1:52 PM, popbuzz me <[email protected]> wrote: > Hi, > > I am developing an app on GAE, and the model that I define has many > properties, around 40, that one of each is large in size. I didn't > consider that as a problem when I was designing it because I think > storage is cheap that I would like to save as much information as > possible. But after I upload the app, i found that writing is very > very expensive, it is around 80,000cpu_ms per write operation, which > is kind of a shock to me. I didn't know that it is that expensive. Do > anyone has the same problem? Is it a better solution to break the > model into smaller pieces then? > > Thanks, > Andy > > -- > 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.
