Well after reading more posts on this subject I have decided it is time to move away from GAE.
I would rather pay $US15 a month for a dedicated tomact that will be always up than have this sort of response times. I would warn any new adopters to think twice before jumping onto GAE until these issues are resolved. Unless of course you have a request per second. On Monday, 4 June 2012 16:18:10 UTC+10, Warwick Slade wrote: > > I am very interested in your thread. > > My app is unloaded very frequently. > > My GWT app issues two ajax calls when it starts up and I see two messages > in the log that the instance has been restarted. > > /event/url1 15:10:05 servlet Context initialised > /event/url2 15:10:16 servlet Context initialised > /event/url1 15:10:24 This request caused a new process to be started for > your application, and thus caused your application code to be loaded for > the first time. > /event/url2 15:10:36 This request caused a new process to be started for > your application, and thus caused your application code to be loaded for > the first time. > > So I what I need to decide is do I > 1. Move my rpc ajax calls onto the service and use the memcache to try and > speed up start time (Will this give me the 200ms response time that I see > when I quickly refresh my browser?) > 2. Forget about using gae and go back to my hosted tomcat solution. > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/edv70D3d-SsJ. 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?hl=en.
