The usage of Appstats on the development environment is to determine
if the request is not performing to many RPC calls.
Doing transactions in a loop is a nice example that might be optimized.
Don't compare the execution times of the development and production.
They have very different implementat
Fredrik, one of the reasons your going to see discrepancies in the numbers
on production is that if your request starts up a new instance than that
request is going to incur the CPU time cost of loading the libraries that
the request uses. Subsequent requests to that instance then won't have that
C
As a followup to this just in case anyone was wondering. The second number
CPU Time does NOT follow the QuotaService convention of not adding the cpu
and api times together and is actually the Total CPU time (CPU time + API
cpu time). IMHO, it really should be renamed to Total CPU so as to not
conf
Thanks for your (both of you) info.
In my mission to improve my application I'm on a constant hunt for
milliseconds. But while improving on every request I find it kinda strange that
the difference would be so huge from my development server.
In appstats the trouble some request that show's "
My understanding (please correct me if I'm wrong) of the log time numbers
are:
1.) Latency time - the amount of actual real world time taken to process the
request. The App Engine infrastructure uses this time to determine if you
are (since it's Christmas time) being naughty or nice. Different num
I always assumed the blue was cpu time and the red api time. Please
feel free to correct me if I am wrong though.
While we're on the topic of appstats does anyone get a zero value
reported for cpu and api times? I only ever get readings such as this:
real=774ms cpu=0ms api=0ms overhead=0ms
Not h
