Greg, thanks for prompt reply. I've raised an issue: * http://code.google.com/p/googleappengine/issues/detail?id=6259*
Anyone feeling it reasonable please start it! To answer your question: *Why we need both Latency & CPU with the new pricing model?* High latency identify there could be sequence of sync calls to API or improper limit. High CPU with low latency can identify here can be a case when we have many async request to API (while we should/can use in-instance cashed data). Does my logic sounds reasonable? At least it works for us. We use this approach to incrementally optimize top handlers one by one. Usually we get 10x improvements - completed 3 iterations at the moment. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/3SnAwvZyQTkJ. 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.
