I installed the AppStats tool in a bid to find out why my simple XML parsing requests were using so much CPU/API time - they run in the blink of an eye on my laptop at home so I couldn't understand why the App Engine was reporting each one took as much as 5 seconds.
To my surprise the AppStats app reported different times. For example: Appstats says: real=886ms cpu=0ms api=0ms overhead=0ms (40 RPCs) Log says: 927ms 3000cpu_ms 2553api_cpu_ms 0kb AppEngine-Google; (+http:// code.google.com/appengine) What's interesting is the response time 927 in the log is _close_ to what appstats records. The cpu/api time is massively different. What appstats reports is what I'd expect - it's just a SAX parse. As it is I have broken the parsing into steps so that it can run at all. Maybe I'm using a dud XML library. Has anyone got any experience with this? Or suggestions? I was hoping AppStats would show me the API issues, but it's just confused me more! Is is possible my code or the app engine has an issue in it that causes false time reporting? It's a bit weird that in a <1s request there can be 3s of CPU time isn't it (or are all of these requests parallel processed when possible in some clever way?) Thanks, Ashley -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" 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-java?hl=en.
