The RPC.Get and RPC.RunQuery can result in many Datastore Read Ops. They can return more then one object and thus read multiple index entries and multiple objects.
Google is able to tally the Datastore Read and Write Ops. Why is there no API call that will return these numbers for the current request? I have changed part of my application to construct and read an aggregate object (containing the attributes of many small objects). The result is that the number of Datastore Read Ops dropped considerable. I'm still having a large number of Read Ops left and have no idea which requests are responsible for the bulk of them. It takes a long time to find the culprit because the billing stats lags quit some time. Op 15 oktober 2011 21:39 heeft Rishi Arora <rishi.ar...@ship-rack.com> het volgende geschreven: > Actually, appstats is more consistent with the old pricing model, and so, it > only shows up number of datastore queries executed, puts and gets, for each > RPC. Here's a screenshot from the link I posted earlier: > http://1.bp.blogspot.com/_dLfQMJsmsaI/S7NKKyRM5-I/AAAAAAAAAEA/rfaOPZXtr80/s1600/Picture+4.png > The request history section shows recent requests, and if you expand a > request, it'll show you datastore puts, gets, and queries. I believe gets > translate to reads one-to-one, but puts depend on how many indexes get > modified in the process. One put will almost always translate to multiple > data store writes (one of each index that gets updated, and one for the > entity being modified) -- 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.
