They use java frameworks which load fast on appengine. I use slim3 (and mvel for templates). There are other options of course. Avoid anything based on reflection, JPA, JDO, etc. And of course live pings is not a solution, and the more people use it, the less it will be.
-- Roberto On Nov 4, 11:32 am, Erwin Streur <[email protected]> wrote: > We have a Java application which uses Spring for dependency injection > and dispatching. The initialization of the WebApplicationContext and > the DispatcherServlet can take upto 20 seconds. When using a regular > webcontainer this is not a problem since initialization is done only > once and at container startup. > > Unfortunately with GAE it becomes a problem. The application has a low > number of requests/min (=1 user request+ 10 system generated > requests / 2 minutes) and we are getting a lot of "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. This request may > thus take longer and use more CPU than a typical request for your > application." > > The result is having slow performance/long response times when > processing user requests and very frequently HardDeadlineExceededError > and thus becoming a serious problem > > I'm curious to know whether other developers have similar issues and > how they addressed them. I haven't made up my mind about the > resolution strategy for this (tweak Spring, remove Spring, add keep a > live pings....) > > Regards, > > Erwin Streur -- You received this message because you are subscribed to the Google Groups "Google App Engine" 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?hl=en.
