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. We haven't looked closely at read operations yet because the writes dwarfs it.
This blog post outlines some unexpected read statistics: http://point7.wordpress.com/2011/09/03/the-amazing-story-of-appengine-and-the-two-orders-of-magnitude/ . I think that using offset with your queries (instead of cursors) could lead to an inflated number of reads. Aside, I'm really surprised that datastore reads cost 70% of a write. I would have expected perhaps an order of magnitude cheaper. j On Sep 6, 7:57 am, Richard Druce <contactd...@gmail.com> wrote: > With the appengine pricing changes, we've been paying attention to our > datastore puts. According to the pricing comparison chart we're making 2.18 > million puts a day. This seems a lot higher than expected. We receive about > 0.6 queries per second which means that each request is making about 60 > puts!! > > Using the sample code for db > profilinghttp://code.google.com/appengine/articles/hooks.htmlwe measured this > for a > day and the most we counted was ~14,000 which seems more reasonable. Does > anyone have experience with something similar on their site? > Thanks, > Richard -- 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.
