Hi all, I've also been battling with with java warmup times. Last week I had startup time of at least 37 seconds. Now it's hovering around 16.
My performance improvements were made by bundling all my dependencies together into a single jar. I've been using the excellent gradle gae plugin (https://github.com/bmuschko/gradle-gae-plugin), which integrates with https://github.com/musketyr/gradle-fatjar-plugin/. This could easily be integrated with an existing gradle project in under an hour. We're using Resteasy, Htmleasy, soy templates, hibernate orm and validator. There were about 60 jars in my WEB-INF/lib. Regards, Will Rayner On Friday, June 22, 2012 1:18:51 PM UTC+10, Thomas Wiradikusuma wrote: > > I have updated > http://code.google.com/p/googleappengine/issues/detail?id=7706 with this > information. > > On Monday, 18 June 2012 11:44:29 UTC+8, Takashi Matsuo (Google) wrote: >> >> On Mon, Jun 18, 2012 at 9:57 AM, Thomas Wiradikusuma >> <wiradikus...@gmail.com> wrote: >> > Just my 2 cents, >> > >> > If indeed our app needs to be single-JARred and obfuscaticated (at >> least removing unused code), IMO that feature should be baked in the tool. >> Probably triggered with extra flag. >> >> I think this is also a good feedback especially if creating the single >> JAR contributes the performance. I'd appreciate it if you could file >> an issue. >> >> -- 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/-/6KSHomHRb1MJ. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
