Looking at my App Engine logs, I see troubling results when viewing the response times for requests. In my current log set, the first 80 requests all complete in under 100 ms with less than 100 ms of cpu or api time. Then, oddly, the 83rd request, from the exact same client with the exact same request parameters, takes 7,192 ms to respond with 10,123 cpu ms (and 12 api ms).
These kinds of spikes are dotted throughout my logs. They occur in less than 1% of cases, as far as I can tell, but the spikes are not just large; they're enormous. I know for a fact that the request parameters and returned data were identical to the requests several seconds before and after from the same client, but the request took about 20 times longer to serve. Does anyone know what causes these large spikes in response time, and can anyone share tricks to help alleviate these spikes? I know that it is somehow related to instantiating the JVM, but I don't know: - how to reduce the startup time of the JVM - how to predict when GAE will try to start a new JVM Thanks in advance for any advice, - Michael -- 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.
