You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Eino Lilius <el...@yahoo.co.uk> on 2005/03/18 13:37:38 UTC

page loading problem

Hi,

I have successfully implemented many pages with
Tapestry. My pages are using heavily components
(template components (just html and jwc, no java
class). 

My problem is that when I access one page (the
heaviest component usage), it takes up to 30 seconds
to open it.
After the page is parsed and I access the page again
it works fast. But after a while the page is parsed
again (after garbage collection?). Is there any way to
declare that a page would be parsed at the server
startup?

Here is how the page works:
The page decides which component it will use based on
the type of the object "A" (contrib:Choose (10
different components)). "A" contains one or many
different objects "B", and the "componentA" will again
use another component for "B" with (contrib:Choose (15
different components)). "B" may again contain some
other objects.

Any other ideas?

Any help would be appreciated! :)

Thanks,
Eino

Send instant messages to your online friends http://uk.messenger.yahoo.com 

---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org


Re: page loading problem

Posted by Kent Tong <ke...@cpttm.org.mo>.
Eino Lilius <elilius <at> yahoo.co.uk> writes:

> My problem is that when I access one page (the
> heaviest component usage), it takes up to 30 seconds
> to open it.

How many components do you have in your .jwc file? 
I doubt that parsing is the bottleneck. Parsing 
is very fast (compared to say DB access) and should 
not take 30 seconds. I'd suggest that you comment out
the components one by one to isolate the problem. 

If it turns out that parsing is really the problem
(again, I doubt it very much), you may try increasing 
the window used the pool:

getEngine().getPool().setWindow(20);

This will allow the pages to stay in the pool idle
for 10 minutes (default is 5 minutes). If it's not 
enough for you, increase it as appropriate.



---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org