[ https://jira.jboss.org/jira/browse/WBRI-357?page=com.atlassian.jira.plugi... ] Pete Muir updated WBRI-357: --------------------------- Description: Grouping issue for suspected performance hotspots If you suspect a performance hotspot, please describe your hunch here. If you have profiling data which shows an issue, please create a new issue, and link to WBRI-359 using "incorportates" -- 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-357?page=com.atlassian.jira.plugi... ] Pete Muir commented on WBRI-357: -------------------------------- An obvious performance hotspot is assignability. It is called for every resolution and more. However, given we cache all resolutions, this may only affect deployment time significantly - this would need verifying, and more caching used if necessary. If it is only a deployment time issue, caching may help, but may also just affect scalability with little improvement as a particular check may only be used once. Options for improvement are limited, but include checking short circuit loops where possible and look at faster algorithms. Another option is to look at performing assignability checks in other threads. -- 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