Seam Performance ?

[gjeudy]

I am using Seam 2.0.1 with Richfaces 3.2.0

I have enabled DEBUG level logging for seam and noticed that on some page requests there is a very long and time-consuming output of entries similar to the below:

2008-04-30 14:36:47,936 DEBUG [org.jboss.seam.Component] instantiating Seam component: org.jboss.seam.core.events

2008-04-30 14:36:47,936 DEBUG [org.jboss.seam.Component] initializing new instance of: org.jboss.seam.core.events

2008-04-30 14:36:47,936 DEBUG [org.jboss.seam.Component] done initializing: org.jboss.seam.core.events

Anybody knows why this is happening? I'm not sure what page content causes this output to be more lengthy on occasions but sometimes it can takes up to 15 secs to render a page on first access. I confirm that database access is not the culprit for my example.

Anybody ran into similar issues, what guidelines should I follow to diagnose this log output?

Thanks,
-Guillaume

[gjeudy]

I think I might be affected by the dataTable performance issue as described in the following JIRA:

JBSEAM-2704

Can anybody else share their experience ? I think this performance issue expands to any iterable JSF component. My example uses:

<h:selectOneListbox id="prodSalesLocationGeographicAreas"

                              required="true" value="#{selectedGeographicArea}" size="10">

                              <s:selectItems value="#{prodSalesLocationGeographicAreas}"

                                   var="geoArea"

                                   label="#{geoArea.typeCd.description}--#{geoArea.geographicAreaNm}" />

                              <s:convertEntity />

                              <a4j:support

                                   action="#{classificationISOAction.selectGeographicArea}"

                                   reRender="coverageGroupsPanel" event="onclick"></a4j:support>

                         </h:selectOneListbox>

[gjeudy]

I've just read this interesting article on how to get better performance: Seam Performance Problem Rewarding Workaround

I think this is probably very near the performance issues I'm having, moreover there is full code to hook in an interceptor to profile performance on calls to seam managed beans. I recommend everyone to use this interceptor to help locate the areas of slowdowns.

On the bright side, Pete Muir from Jboss Seam confirmed they are working on improving performance of the framework. I am looking forward for a seam release adressing these issues. Any projected dates as to when this might happen ?

Thank you,
-Guillaume