Hi Dmitry, thanks for this information. 20 seconds to first page is indeed pretty long, but if you use a cron-job to keep the application warm, the long startup time is less of an issue. This was one of my major doubts about Tapestry on GAE, but your approach seems like a very good work-around.
regards, Onno On Wed, Aug 26, 2009 at 11:02 AM, Dmitry Gusev <dmitry.gu...@gmail.com>wrote: > It tooks 15 seconds to startup the instance + 5 seconds to render the first > page (same on my development laptop and GAE cloud) > > Thats pretty long but I guess the bottleneck here is not in tapestry but > rather in spring. > > As for cleaning up an instance after it's not being used - I can't tell > you, > thats not my case. I've set up cron triggers for executing ping jobs and > those triggers actually invoke HTTP GET on my tapestry pages, so the app is > always warm. > > On Wed, Aug 26, 2009 at 11:12, Onno Scheffers <o...@piraya.nl> wrote: > > > > > @Dmitry > > Sorry for hijacking your thread like this. Tapestry on GAE looks very > > interesting to me. > > I was wondering how long it takes for the first page to render after the > > application has just been deployed/suspended. If I'm not mistaken, GAE > will > > have cleaned up your instance if it isn't being used much and will have > to > > restart the application. > > Applications made up of servlets and JSPs will be running very quickly, > but > > I guess a framework like Tapestry that has to initialize a lot of > services > > might take a bit longer? > > > > > > regards, > > > > Onno > > > > > > -- > Dmitry Gusev > > AnjLab Team > http://anjlab.com >
