You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by John Singleton <jo...@looseend.org> on 2006/06/07 18:26:02 UTC

Re: Portlet performance


Jesse Kuhnert <jkuhnert <at> gmail.com> writes:

> 
> First I've heard of it. I didn't initially have plans on doing anything with
> it but I'd be happy to in order to save you from jsf. :)
> 
> Whatever "it" is probably won't happen in the initial alpha release as I
> have some other items taking higher priority, but if you start a jira issue
> with some clear parameters for me to test with we can probably figure
> something out.
> 
I've done a few more timings, and it seems like the Registry construction isn't
the culprit.

ApplicationPortlet.init takes about 2.5s (.6 of which is the constructRegistry
call). The initial render takes 4.5s . Will this initial hit be when it
constructs the State Object that I am injecting?

I'll create a Jira issue, but just wanted to make sure I wasn't doing something
silly first.

Thanks

John


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