We also have a large number of Datastore Write ops in our sample bill, and we figured out that it was likely due to properties with indexed=True thanks to the Quota Details admin page that gives more detail:
Datastore CPU Time 0% 431.12 of Unlimited CPU hours Datastore Entity Fetch Ops 0% 8,288,728 of Unlimited Datastore Entity Put Ops 0% 4,159,838 of Unlimited Datastore Entity Delete Ops 0% 1,072,478 of Unlimited Datastore Index Write Ops 0% 37,251,177 of Unlimited Datastore Query Ops 0% 642,110 of Unlimited Datastore Key Fetch Ops 0% 4,403,176 of Unlimited Here we clearly see that it's "Datastore Index Write Ops" that is responsible for an expensive bill. We will see soon the impact of having indexed=False on most properties. Hope it helps On 7 sep, 13:23, Stephen <sdeasey+gro...@gmail.com> wrote: > On Tue, Sep 6, 2011 at 10:05 PM, Jason Collins > > <jason.a.coll...@gmail.com> wrote: > > > We are seeing a lot more datastore write operations than we can > > account for (375M / day). Still trying to get to the bottom of it > > because it makes for a scary line item on the new sample bills. > > Divide 375M writes by number of request to get the average writes per > request. Use code similar to the following to log requests with more > > than average writes: > > https://gist.github.com/715284 > > Should home in on the write-happy code pretty quickly. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
