If you haven't read the following articles, they are a good place to start. In particular, note that multiple repeated properties in your custom indexes can cause unanticipated numbers of writes.
https://developers.google.com/appengine/articles/storage_breakdown https://developers.google.com/appengine/articles/indexselection We do not allow dev_appserver to automatically write index.yaml so that devs have to explicitly manage the indexes as their queries change (make sure you start dev_appserver with --require_indexes to get exceptions for missing indexes). We've found that if we don't explicitly manage the indexes, we get all sorts of unused ones created through the development process. Also, I'm sure you're aware, but you can set indexed=False on any property, which actually removes 2 datastore writes per put (up to 4 on an update) because an ASC and DESC index is managed under the hood on your behalf. j On Tuesday, 19 February 2013 19:19:28 UTC-6, Scott Hunter wrote: > > Within the last accounting period, I've racked up 300 Datastore Put Ops, 0 > Datastore Delete Ops, but managed over 15,000 Datastore Index Writes! I > only have 3 indices on the entity being written to, two with 3 properties > and one with 6. > > Is there something I can do to reduce these Index writes? For example, > remove one or more indices (assuming I can re-write my queries so as not to > need them, or they'll just come right back)? > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
