[ https://jira.jboss.org/jira/browse/WBRI-358?page=com.atlassian.jira.plugi... ] Pete Muir updated WBRI-358: --------------------------- Description: Grouping issue for suspected scalability hotspots If you suspect a scalability hotspot, describe your hunch here. If you have profiling or load testing which confirms a hotspot, please create a new issue and link to WBRI-360. -- 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/WBRI-358?page=com.atlassian.jira.plugi... ] Pete Muir commented on WBRI-358: -------------------------------- An obvious scalability issue will be the reflection layer, which performs extensive caching to speed up usage. It scales at O(CM) where C is the number of classes, M is the no of members in a class which reduces to O(N^2). Options include: * Expose to container so it provides an impl - someone elses problem * Perform analysis, and for infrequently used operations perform direct access to class or member with no caching * Verify that no uneeded data is stored * Investigate lazy initialization (concurrency issues abound) * Investigate discarding information once bean definition is built, or provide ability to create runtime version -- 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