Hi Jeff, How about optimizing with ProGuard (http://proguard.sourceforge.net/ index.htm). It preform death code elimination and repackage to single jar file.
KT On Jun 17, 5:56 am, Jeff Schnitzer <[email protected]> wrote: > We're having a big problem with instance startup time. It varies > between 20s and 60+ seconds, and lately it's tending towards the high > end. We're starting to experience downtime because instances get > deadlined before they go active. > > This app is well optimized for GAE. There's no classpath scanning and > it doesn't try to eagerly load data. On a good day it starts in > 20s... so at this point there's not really much I can do. > > I have a cron task that performs a db cleanup once a minute, and since > crons can run over 60s I can eventually get one instance started, > which is enough to serve traffic at the moment. But at this point I > can no longer deploy code over old versions because the appserver > restart will fail. > > Please help. > > Jeff -- 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.
