I understand that there can be problems with everyone having a full- time reserved JVM. My problem is simply that the instance restarts too frequently. I mean, honestly, one SINGLE page request results in TWO application restarts? Even if you get it down to 4 seconds, that's 8-10 seconds just for the page to load.
I confess, I'm not an expert on the technology involved. Is it technologically difficult to say, if a JVM gets any traffic, hold it open for 5 minutes at a minimum. This can be cheated by the "keep alive" pinging that people are doing, but perhaps that can be ignored and only external traffic counts? Jake On Jun 3, 8:21 pm, Thomas <mylee...@gmail.com> wrote: > > I use struts 1.2.x + Spring 2.0 initially. But quickly I realized > > I had to get rid of Spring in order to decrease the startup time. So I > > wrote a TidyDelegationProxy (tidy means TIny DependencY injector) to > > replace Spring's struts proxy. I successfully reduced the startup CPU > > time from 12+ seconds to 6 seconds. > > Correct some mistakes. > I use struts 1.2.x + Spring 2.0 + JDO initially. But quickly I > realized I had to get rid of Spring and JDO in order to decrease the > startup time. So I > used slim3 and wrote a TidyDelegationProxy to replace Spring's struts > proxy. I successfully reduced the startup CPU time from 12+ seconds to > 6 seconds. -- 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-j...@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.
