I think (and previous guidance supports this) that it isn't the loading of the jars that is taking time, its actually fetching your war (and the files in it, so *down*loading the jars) that is taking so much elapsed time. The smaller your overall artifact, the quicker it can be pulled in and started up.
Its interesting looking at some of my apps which jars are unusually large. Guava itself is surprisingly large (10% of my average war). Might be worth playing a little with to see how much this can be optimised. On Tuesday, February 18, 2014 7:33:16 AM UTC+11, Emanuele Ziglioli wrote: > > Not sure where my reply went. > > On Tuesday, February 18, 2014 3:57:37 AM UTC+8, Emanuele Ziglioli wrote: >>> >>> Our warmup time was 15 seconds, then I looked at the hello world project >>> that the GAE plugin generates with one servlet. >>> That took 2 seconds to startup (once the servlet was hit). >>> >> >> On F2 instance? >> > > Haven't seen much difference between F1 and F2 when it comes to warmup > time. > Most time seems to be spent actually loading jars. Initialization could be > as little as 3s with our project, F2 would a bit better but not so much > >> >> My experience is the modules feature will spend your money. >> > > I haven't seen many people using modules yet. Can't they be configured to > be F1 like non default versions? > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
