That's interesting, that GAE shuts down your instances. There's a bit of Tapestry based on the idea that the application is long running, so it's OK if it takes a moment to start up initially. Under GAE that's not the case ... perhaps Tapestry under GAE should be even a bit lazier about loading and instantiating.
When GAE shuts down the instance, is it undeploying the WAR? All told, I think the most significant amount of time spent starting up a T5 app is the initial load of all those classes. I can see these during the Selenium integration tests, where the second test app to start up (all within the same JVM) is much faster because all the framework classes have already been loaded. On Mon, Jun 7, 2010 at 7:01 AM, Thiago H. de Paula Figueiredo < thiag...@gmail.com> wrote: > On Mon, 07 Jun 2010 10:42:52 -0300, Dmitry Gusev <dmitry.gu...@gmail.com> > wrote: > > This is exactly what I mean, I don't want tapestry to load even once for >> some requests. GAE shutdown/startup instances very often (one new instance >> per ~3 minues) and this consumes additional resources. >> > > Oops, I forgot this GAE characteristic and what you said makes sense now. > :) > > -- > Thiago H. de Paula Figueiredo > Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, > and instructor > Owner, Ars Machina Tecnologia da Informação Ltda. > http://www.arsmachina.com.br > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com
