[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2704) Performance during iteration (datatable, repeat) in the UI with value bindings that run through interceptors

Stuart Douglas (JIRA) jira-events at lists.jboss.org
Wed Oct 1 22:25:21 EDT 2008


    [ https://jira.jboss.org/jira/browse/JBSEAM-2704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12432093#action_12432093 ] 

Stuart Douglas commented on JBSEAM-2704:
----------------------------------------

Would it be possible to defer disinjection for specially marked components until after the render response phase is complete? The marked components would only be injected once the first time they are invoked, and the values remain injected until the end of the phase where come kind of clean up code disinjects them?

> Performance during iteration (datatable, repeat) in the UI with value bindings that run through interceptors
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: JBSEAM-2704
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-2704
>             Project: Seam
>          Issue Type: Task
>          Components: Performance and Scalability
>    Affects Versions: 2.0.0.GA, 2.0.1.GA
>         Environment: Seam 2.0.0, 2.0.1
>            Reporter: Siarhei Dudzin
>
> "Since we don't cache this, a particular backing bean might be called hundreds or thousands of times during rendering of a datatable, if a value binding has to be evaluated for each row. If the backing bean is a Seam component, injection of dependencies will occur for every call, involving potentially thousands of map lookups."
> There is a discussion thread with a bit more data: http://www.seamframework.org/Community/SeamPerformanceOptimization
> The issue is also recognized at the seamframework.org site itself: http://www.seamframework.org/Documentation/TuningTheSeamWebsite#H-IterationDatatableRepeatInTheUIWithValueBindingsThatRunThroughInterceptors
> Since the issue it known, this JIRA report is created for better traceability.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the seam-issues mailing list