Hi, I decided to do some long-run performance tests on my application. I created some small client hitting app every 5-30 minutes and I run 3-5 of threads with such client.
I noticed huge differenced in response times and started to investigate issue. I found reason very quick. I am experiencing same issues as described in following topics: http://groups.google.com/group/google-appengine/browse_thread/thread/fed86730708f2a9d/c6f13c9c48c08791?lnk=gst&q=request+response+time#c6f13c9c48c08791 http://groups.google.com/group/google-appengine/browse_thread/thread/7cd20b6fcfd38e5d http://groups.google.com/group/google-appengine-java/browse_thread/thread/755b7ba89db70213/4b39d900479ba1de?lnk=gst&q=application+instance#4b39d900479ba1de I am using Springframework, it tkes around 18-20s to start app instance, which is causing response times to take from 1s (when requests hits running app - very rare) to 22s when fresh application is created. Is there any solution for this? I was thinking about creating most basic servlet performing critical tasks (serving API call) and leave UI as is. But then I would loose all benefits of Springframework. Is there any solution for this? After solving (hacking) numerous constrains of App Engine which I hit while developing my app that is the one I think will make me move out of App Engine... that's simply to much to all the time think how to win with GAE problems than how to solve my application problems... Any help? Regards Konrad
-- 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.
