Re: Live class reloading very slow
Hi, your suggestion did improve reload when only template is changed. Still 6 seconds reload happens when I change page class. Hope this is also abnormal and someone has some suggestions how to fix it as well. to clarify : adding exclude ** for resources will stop eclipse from doing anything there, and this was wrong until I restored defaults for m2eclipse. by doing this maven added it's own resource processing to the build. After that templates get copied as soon as edited, Unlike with eclipse builder page reload is very fast 200ms for a page that reloaded 6 seconds before the changes were made. Davor Hrg On Tue, May 24, 2011 at 7:49 PM, Bryan Lewis jbryanle...@gmail.com wrote: I put it back into the src/main/resources line of .classpath, like: classpathentry excluding=** kind=src output=target/classes path=src/main/resources/ My templates are being copied to the expected place, like ... target\classes\com\companyname\appname\pages\PageName.tml. Maybe there's something else amiss with your maven/build configuration. Does your pom.xml have the resources section? Maybe compare your configuration with a small new one like the Tapestry quickstart. On Tue, May 24, 2011 at 1:37 PM, Davor Hrg hrgda...@gmail.com wrote: I also removed excluding ** for src/main/resurces but without it templates do not get copied to calsses dir where did you put back the excluding ** ? Davor Hrg
Re: Live class reloading very slow
You don't have to copy the templates anywhere. It still may not explain why class reloading is slow for you, but file IO is fairly expensive and thus should be avoided. Kalle On Wed, May 25, 2011 at 1:17 AM, Davor Hrg hrgda...@gmail.com wrote: Hi, your suggestion did improve reload when only template is changed. Still 6 seconds reload happens when I change page class. Hope this is also abnormal and someone has some suggestions how to fix it as well. to clarify : adding exclude ** for resources will stop eclipse from doing anything there, and this was wrong until I restored defaults for m2eclipse. by doing this maven added it's own resource processing to the build. After that templates get copied as soon as edited, Unlike with eclipse builder page reload is very fast 200ms for a page that reloaded 6 seconds before the changes were made. Davor Hrg On Tue, May 24, 2011 at 7:49 PM, Bryan Lewis jbryanle...@gmail.com wrote: I put it back into the src/main/resources line of .classpath, like: classpathentry excluding=** kind=src output=target/classes path=src/main/resources/ My templates are being copied to the expected place, like ... target\classes\com\companyname\appname\pages\PageName.tml. Maybe there's something else amiss with your maven/build configuration. Does your pom.xml have the resources section? Maybe compare your configuration with a small new one like the Tapestry quickstart. On Tue, May 24, 2011 at 1:37 PM, Davor Hrg hrgda...@gmail.com wrote: I also removed excluding ** for src/main/resurces but without it templates do not get copied to calsses dir where did you put back the excluding ** ? Davor Hrg - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: Live class reloading very slow
Hi Davor, Have you tried running Jetty standalone, out of eclipse? This is what we do. I'm not sure it has anything to do with your problem but it might be worth a try. It's only a few lines of code to write a simple Jetty server launcher as you can see http://pastebin.com/WsEFi2yh Just write a simple script to run for this class and even though you'll be using Jetty outside of eclipse you can still make code changes in eclipse and it will reload them dynamically (as long as you set your classpath for the jetty startup script correctly). - J On Wed, 2011-05-25 at 10:17 +0200, Davor Hrg wrote: Hi, your suggestion did improve reload when only template is changed. Still 6 seconds reload happens when I change page class. Hope this is also abnormal and someone has some suggestions how to fix it as well. to clarify : adding exclude ** for resources will stop eclipse from doing anything there, and this was wrong until I restored defaults for m2eclipse. by doing this maven added it's own resource processing to the build. After that templates get copied as soon as edited, Unlike with eclipse builder page reload is very fast 200ms for a page that reloaded 6 seconds before the changes were made. Davor Hrg On Tue, May 24, 2011 at 7:49 PM, Bryan Lewis jbryanle...@gmail.com wrote: I put it back into the src/main/resources line of .classpath, like: classpathentry excluding=** kind=src output=target/classes path=src/main/resources/ My templates are being copied to the expected place, like ... target\classes\com\companyname\appname\pages\PageName.tml. Maybe there's something else amiss with your maven/build configuration. Does your pom.xml have the resources section? Maybe compare your configuration with a small new one like the Tapestry quickstart. On Tue, May 24, 2011 at 1:37 PM, Davor Hrg hrgda...@gmail.com wrote: I also removed excluding ** for src/main/resurces but without it templates do not get copied to calsses dir where did you put back the excluding ** ? Davor Hrg - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: Live class reloading very slow
Tomcat or Jetty? I forget why (perhaps I can dig out the details) but I found class reloading on Tomcat was very slow - so I switched to Jetty which is essentially instantaneous - very quick. On Tue, 2011-05-24 at 17:37 +0200, Davor Hrg 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 - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: Live class reloading very slow
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
Re: Live class reloading very slow
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
Re: Live class reloading very slow
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
Re: Live class reloading very slow
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
Re: Live class reloading very slow
Maybe you did the same thing I did? http://tapestry.1045711.n5.nabble.com/slow-page-reload-td4287502.html On Tue, May 24, 2011 at 1:06 PM, Davor Hrg hrgda...@gmail.com wrote: 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
Re: Live class reloading very slow
Honestly, we have a pretty complex app: multiple zones, lots of and nested components, loads of injected assets, services etc and it reloads faster than I can hit F5. On Tue, 2011-05-24 at 19:06 +0200, Davor Hrg wrote: 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 - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: Live class reloading very slow
I also removed excluding ** for src/main/resurces but without it templates do not get copied to calsses dir where did you put back the excluding ** ? Davor Hrg
Re: Live class reloading very slow
I put it back into the src/main/resources line of .classpath, like: classpathentry excluding=** kind=src output=target/classes path=src/main/resources/ My templates are being copied to the expected place, like ... target\classes\com\companyname\appname\pages\PageName.tml. Maybe there's something else amiss with your maven/build configuration. Does your pom.xml have the resources section? Maybe compare your configuration with a small new one like the Tapestry quickstart. On Tue, May 24, 2011 at 1:37 PM, Davor Hrg hrgda...@gmail.com wrote: I also removed excluding ** for src/main/resurces but without it templates do not get copied to calsses dir where did you put back the excluding ** ? Davor Hrg
