Hi John I'm afraid I cannot offer any specific suggestions, but I it may be worth looking at the Objectify persistence framework, one of its primary goals was to reduce start up time. If nothing else, trawling the documentation may give you some valuable clues
On Aug 4, 2:57 am, John <jwb...@gmail.com> wrote: > As our app has grown, the amount of initialization work to do in order to > make an instance useful has increased to the point that GAE often terminates > requests that start a new instance. We had a warmup servlet, but the work > started to commonly exceed the deadline. We're now looking to pare down the > warmup, but we're having trouble with tuning since the behavior seems pretty > different on the dev server from GAE. On the dev server, the initialization > (loading our initial servlets) will complete in the vicinity of 4sec while > GAE instance startup is often more than 20sec. We often see inexplicable > gaps in our logging of 15sec or more (seemingly hung up), but it doesn't > seem repeatable. > > Our focus to date has been to optimize the JDO/Datanucleus startup, but we > believe that a significant contributor might be the number of classes > loaded. Is it accurate to conclude that class loading carries a larger > overhead on GAE than other environments? Are there any tools that will help > us understand the processing during this startup? The Appstats tool shows > long delays, but we don't know what is taking time besides the RPCs. -- 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 google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
