Appstats is what you are looking for. http://code.google.com/appengine/docs/python/tools/appstats.html http://code.google.com/appengine/docs/java/tools/appstats.html
Also look at http://code.google.com/appengine/docs/billing.html You will see that different kinds of queries and operations use a different number of operations. If you can key-get your entities instead of querying on them, you use half as many operations. If you wrap your puts and gets with memcache put and get, you can skip lots of excess DS reads. If you can somehow use browser caching for some of your queries, you can cut not only DS reads but http requests as well. {hint: if you keep an updated timestamp, you can use this as last- modified or to generate etags so browser can cache it, but get updates when available}. Anyway, these are just general solutions. Plugin appstats and it will show you where all your excess usage is. On Dec 6, 11:44 am, cloudpre <[email protected]> wrote: > Hi - my app is taking more than 12M reads in less than 10 hours- is > there a tuner to check which calls are exhibiting this weird behavior? > > I mean how do we tune this? > > Thanks. -- 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.
