I had this problem as well. Basically your app is running a a Google controlled JVM somewhere. After X seconds of not being used (where X is a number decided on Google based on load, etc) your JVM shuts down. When you get a new request, it has to start up, and then server the request. A simple jsp may take 600ms.. but a full fledged MVC like my current app runs takes ~6000 ms. Really bad.
Here is how I solved the problem for the full JVM startup. 99% of my page did not really need to be a jsp, it was static html. So I made a static .html file and put it in my static directory. These are always available, and served instantly. So I load the bulk of my page like that, start rendering the page, downloading images, etc. etc. When the page is loaded I do an ajax request to my server, which does the jsp magic, and returns me an html view of the computed JSP and I stick it on the page. I am personally using Prototype and Ajax.Updater, but there are many ways to do this. Basically, a 90% rendered page with a 6000 ms lag is much much less bad than a page that does nothing for 6000ms. There is enough other animation and stuff going on that it doesn't seem super bad. So yes, this is a little bit of a pain, but it may be what we have to put up with for now. Ideally someday we can pay to keep our instances always "on", but we will see on that... On Feb 12, 6:27 pm, Spines <[email protected]> wrote: > Anyone know? -- 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.
