[ http://jira.jboss.com/jira/browse/JBSEAM-2704?page=all ] Christian Bauer updated JBSEAM-2704: ------------------------------------ Issue Type: Task (was: Bug) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBSEAM-2704?page=comments#action_12412692 ] Tobias Hill commented on JBSEAM-2704: ------------------------------------- Here is more data about it: http://www.seamframework.org/Community/SeamPerformanceProblemRewardingWor... That thread lands in a "workaround DTO-pattern" for avoiding the repeated injection-overheads. It also provides some tools for finding similar problems over the set of beans (Pojos or SxSB) you have in your application. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-2704?page=com.atlassian.jira.pl... ] Pete Muir updated JBSEAM-2704: ------------------------------ Summary: Document patterns which improve performance (was: Performance during iteration (datatable, repeat) in the UI with value bindings that run through interceptors) Fix Version/s: 2.1.1.CR1 Description: Umbrella issue for documenting patterns which can improve the performance of your Seam app. (was: "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-Iterati... Since the issue it known, this JIRA report is created for better traceability.) Assignee: Shane Bryzak Priority: Critical (was: Major) "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-Iterati... 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

[ https://jira.jboss.org/jira/browse/JBSEAM-2704?page=com.atlassian.jira.pl... ] Shane Bryzak closed JBSEAM-2704. -------------------------------- Resolution: Done I've added a new chapter to the documentation called "Performance Tuning" and started it off by describing @BypassInterceptors and when it should be used. We'll probably add more content to this chapter as time goes on. -- 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