I have a app that I thought would be perfect for the google app engine. Mostly idle, but for periods could be fairly high demand. Very simple workflow, no user request should take more than 2 seconds server side.
To prototype it out, I used the stripes framework to get a simple MVC setup. This works very well when it is up (<200ms server time per request), but is very very bad when the server needs to warm up to a new request (10-12 seconds). I know stripes is a very slow framework on server startup time, and apparently it needs to start up after being idle for a few minutes on GAE. Before I go down the patch of switching MVCs, I would be interested in a) What framework are you using b) What is the time taken from a cold start? (i.e. time to do a request when app is cold - time it normally takes to do the request). I am okay with a 3 or 5 second lag to get an instance going, but a 10-12 second hit is too much. If no framework gets much better, then I guess I will switch to a static index.html that loads the page via JavaScript. -- 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.
