Hi,
I noticed that in v4.0 first page display takes much longer than in v 3.0.3:
15 sec vs 7 sec.
I used the helloworld application for testing.
My environment is:
JBoss 4.0.2 (also tried Jetty and Tomcat, same result)
Sun JDK 1.5.06
Intel Celeron 1.7GHz Laptop
512 MB RAM
Debian Linux Unstable (also tried in Windows, same result)
Is there any way to improve this time?
Thanks,
Alex
To unsubscribe, e-mail: tapestry-user-unsubscribe (AT) jakarta (DOT) apache.org
For additional commands, e-mail: tapestry-user-help (AT) jakarta (DOT) apache.org

I seem to remember you already asked this question and there were several
responses. Did you see them?

Gregg

1/13/06, Alexander Varakin <avarakin (AT) gmail (DOT) comwrote:

Hi,

I noticed that in v4.0 first page display takes much longer than in v
3.0.3:
15 sec vs 7 sec.
I used the helloworld application for testing.
My environment is:
JBoss 4.0.2 (also tried Jetty and Tomcat, same result)
Sun JDK 1.5.06
Intel Celeron 1.7GHz Laptop
512 MB RAM
Debian Linux Unstable (also tried in Windows, same result)

Is there any way to improve this time?

Thanks,
Alex
>
>
>

To unsubscribe, e-mail: tapestry-user-unsubscribe (AT) jakarta (DOT) apache.org
For additional commands, e-mail: tapestry-user-help (AT) jakarta (DOT) apache.org
--

I believe what you're seeing is just the way it is at this point in
time. The extra time is used for things like building the Hivemind
registry. If you turn on debug logging for Tapestry you'll see all the
work that's being done at startup.

In this earlier posting:
%3C001401c5b1cf$4488cd90$800101df@adamgreene%3E

Howard said:

I'm not thrilled with the slow startup of Tapestry 4, but it's a case
of "get it right, then get it fast". I'll be looking at ways to speed
up HiveMind for 1.2, then see if we can make use of that in Tapestry
4.1. I am pleased that runtime performance is good and, I suspect,
better than 3.0.

I agree that it's somewhat frustrating. After upgrading to Tap4, I've
spent some time looking for the best development environment (trying
things like JettyLauncher and JBossIDE) that would let me avoid
restarting the server and Tapestry whenever possible. I haven't been a
Spindle user before now, but I'm hoping the future Spindle4 will allow
something like a hot-code-replace feature.

Alexander Varakin wrote:

>Hi,
>
>I noticed that in v4.0 first page display takes much longer than in v 3.0.3:
>15 sec vs 7 sec.
>I used the helloworld application for testing.
>My environment is:
JBoss 4.0.2 (also tried Jetty and Tomcat, same result)
Sun JDK 1.5.06
Intel Celeron 1.7GHz Laptop
512 MB RAM
Debian Linux Unstable (also tried in Windows, same result)
>
>Is there any way to improve this time?
>
>Thanks,
>Alex
>

>
>
>To unsubscribe, e-mail: tapestry-user-unsubscribe (AT) jakarta (DOT) apache.org
>For additional commands, e-mail: tapestry-user-help (AT) jakarta (DOT) apache.org
>

To unsubscribe, e-mail: tapestry-user-unsubscribe (AT) jakarta (DOT) apache.org
For additional commands, e-mail: tapestry-user-help (AT) jakarta (DOT) apache.org

Sorry for double posting: I sent this message twice: 1st from a wrong e-mail
account, then I realized that I made a mistake and sent it from a right
account. Looks like the 1st message was released today.

BTW, if I run tapestry in Eclipse using Jetty Launcher or Tomcat Launcher in
debug mode, it takes even longer for 1st page display - about 40 sec.
I profiled the program and it looks like all time is taken in memory
allocations.

Alex

Monday 16 January 2006 02:23 pm, Gregg Bolinger wrote:
I seem to remember you already asked this question and there were several
responses. Did you see them?

Gregg

1/13/06, Alexander Varakin <avarakin (AT) gmail (DOT) comwrote:
Hi,

I noticed that in v4.0 first page display takes much longer than in v
3.0.3:
15 sec vs 7 sec.
I used the helloworld application for testing.
My environment is:
JBoss 4.0.2 (also tried Jetty and Tomcat, same result)
Sun JDK 1.5.06
Intel Celeron 1.7GHz Laptop
512 MB RAM
Debian Linux Unstable (also tried in Windows, same result)

Is there any way to improve this time?

Thanks,
Alex
>
>
>

To unsubscribe, e-mail: tapestry-user-unsubscribe (AT) jakarta (DOT) apache.org
For additional commands, e-mail: tapestry-user-help (AT) jakarta (DOT) apache.org

To unsubscribe, e-mail: tapestry-user-unsubscribe (AT) jakarta (DOT) apache.org
For additional commands, e-mail: tapestry-user-help (AT) jakarta (DOT) apache.org

Hot-code-replace feature is available in Eclipse if you run web container in
debug mode. The problem is that it takes twice longer to display first page
in debug mode. Also Hot-code-replace works only if you don't touch function
declarations.

I agree that it's somewhat frustrating. After upgrading to Tap4, I've
spent some time looking for the best development environment (trying
things like JettyLauncher and JBossIDE) that would let me avoid
restarting the server and Tapestry whenever possible. I haven't been a
Spindle user before now, but I'm hoping the future Spindle4 will allow
something like a hot-code-replace feature.

Alexander Varakin wrote:
>Hi,
>
>I noticed that in v4.0 first page display takes much longer than in v
3.0.3: 15 sec vs 7 sec.
>I used the helloworld application for testing.
>My environment is:
JBoss 4.0.2 (also tried Jetty and Tomcat, same result)
Sun JDK 1.5.06
Intel Celeron 1.7GHz Laptop
512 MB RAM
Debian Linux Unstable (also tried in Windows, same result)
>
>Is there any way to improve this time?
>
>Thanks,
>Alex
>
>
>
>
>To unsubscribe, e-mail: tapestry-user-unsubscribe (AT) jakarta (DOT) apache.org
>For additional commands, e-mail: tapestry-user-help (AT) jakarta (DOT) apache.org
>

To unsubscribe, e-mail: tapestry-user-unsubscribe (AT) jakarta (DOT) apache.org
For additional commands, e-mail: tapestry-user-help (AT) jakarta (DOT) apache.org

To unsubscribe, e-mail: tapestry-user-unsubscribe (AT) jakarta (DOT) apache.org
For additional commands, e-mail: tapestry-user-help (AT) jakarta (DOT) apache.org

I must be doing something wrong then. I've tried three app servers,
currently trying JBoss/Tomcat. Running inside Eclipse, starting in
debug mode. I have Tapestry's caching disabled in the startup
properties, and changes to the html or page files do take effect
immediately. But when I make a small change inside a Java method it
does get built automatically, and the class file does get updated in
the webapp tree. But the change doesn't show up in the browser until I
restart the server or reload the app.

Alexander Varakin wrote:

>Hot-code-replace feature is available in Eclipse if you run web container in
>debug mode. The problem is that it takes twice longer to display first page
>in debug mode. Also Hot-code-replace works only if you don't touch function
>declarations.
>

To unsubscribe, e-mail: tapestry-user-unsubscribe (AT) jakarta (DOT) apache.org
For additional commands, e-mail: tapestry-user-help (AT) jakarta (DOT) apache.org