I've updated run-jetty, and tried with and without page-pool still 5-6 seconds load time.
I decided to try to go as simple as possible ... empty page with layout component takes 500 ms - add a form .. it jumps to 700 ms - add few submit buttons ... jumps to 800 ms - add a component with a zone inside it .. jumps to 950 ms - add two more of same component and few lines of text ... jumps to 1200 ms This is awful ... I hope this can be fixed by configuring something ... etc... if this is T5 reality ... it is extremely unproductive and painful. :( :( :( Davor Hrg On Tue, May 24, 2011 at 6:26 PM, Joel Halbert <j...@su3analytics.com> wrote: > Hi Davor, > > I use a similar spec. Should take a second or two. > > - Joel > > On Tue, 2011-05-24 at 18:10 +0200, Davor Hrg wrote: > > ok, > > > > we are on 5.2.4 now, > > I am running it from eclipse using run-jetty-run 1.1.1 > > I'll try newer jetty plugin 1.2.2.1 > > > > how long should I expect a page reload to last for: > > - page > > - editing component inside > > - two forms in the component > > - maybe 20 form fields total > > > > Quad core intel Core i7 > > 4GB RAM > > > > Davor Hrg > > > > On Tue, May 24, 2011 at 5:50 PM, Howard Lewis Ship <hls...@gmail.com> > wrote: > > > > > For me as well, instantaneous under Jetty. > > > > > > 5.2.5 adds "field write-behind" when in development mode, to assist > > > with debugging. This is also present in 5.3. > > > > > > There is a switch to use the page pool, please chck the documentation > > > (configuration page). > > > > > > On Tue, May 24, 2011 at 8:37 AM, Davor Hrg <hrgda...@gmail.com> wrote: > > > > Hi, > > > > > > > > I may be wrong but since T5 5.2+ > > > > live class reloading is much slower. > > > > > > > > I remember it being faster before .... > > > > for a page with maybe 10-20 components > > > > reload lasts for 5-10 seconds. > > > > > > > > it becomes worse with each component added. > > > > > > > > This is far from productive and far from advertised by the framework. > > > > It feels like going back to stone age of JSP and restarting whole > server > > > for > > > > simple change. > > > > > > > > We have been using tapestry since the beginning of T5, and a bit T4, > > > > I could swear it was not this horribly slow before. > > > > > > > > > > > > Another thing is the new handling of variables and page pool. > > > > it is awful for debugging... is there a switch to use old page pool ? > > > > > > > > Davor Hrg > > > > > > > > > > > > > > > > -- > > > 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 > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > > > For additional commands, e-mail: users-h...@tapestry.apache.org > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
