I was testing the load times in various languages last night, as shown in another group:
http://groups.google.com/group/google-appengine/browse_thread/thread/11b2f2b425e10e38 But at one point, my Java "hello, world" servlet was killed for taking too long to respond (10 seconds seems to be the undocumented limit here). This was merely running the example template code provided by Google. The load requests made before and after worked (with wildly different response times). There must be some serious problems with the way AppEngine is loading Java code if "hello, wold" is canceled for excessive latency! Is Google aware of this? I know they are hoping to improve Java performance, but this is a more serious issue. No matter how well you optimize your Java code, you can't do anything about the AppEngine loader itself crashing... 01-18 08:50PM 42.121 /helloappengine 500 10085ms 0cpu_ms 0kb Mozilla/ 5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7 (.NET CLR 3.5.30729),gzip(gfe) [myip] - - [18/Jan/2010:20:50:52 -0800] "GET /helloappengine HTTP/1.1" 500 0 - "Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7 (.NET CLR 3.5.30729),gzip(gfe)" "[myapp]" W 01-18 08:50PM 52.206 Request was aborted after waiting too long to attempt to service your request. Most likely, this indicates that you have reached your simultaneous dynamic request limit. This is almost always due to excessively high latency in your app. Please see http://code.google.com/appengine/docs/quotas.html for more details. -- 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.
