[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2917) Bad cache in getEjbDescriptor

Shane Bryzak (JIRA) jira-events at lists.jboss.org
Wed Apr 23 06:22:44 EDT 2008


    [ http://jira.jboss.com/jira/browse/JBSEAM-2917?page=comments#action_12410188 ] 
            
Shane Bryzak commented on JBSEAM-2917:
--------------------------------------

This is probably just one of many performance improvements that we can potentially make, we could probably backport it to 2.0.2 (although the code will be different as these methods have changed).  I think we should be focused on a more formal profiling and performance effort for 2.1.0, rather than any 'here and there' minor fixes we can squeeze into 2.0.2.

> Bad cache in getEjbDescriptor
> -----------------------------
>
>                 Key: JBSEAM-2917
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-2917
>             Project: Seam
>          Issue Type: Bug
>    Affects Versions: 2.0.2.CR1
>            Reporter: Clint Popetz
>         Assigned To: Shane Bryzak
>             Fix For: 2.1.0.BETA1
>
>         Attachments: seam-getEjbDescriptor-cache.patch
>
>
> Seam.getEjbDescriptor re-initializes its cache of descriptors every time it fails to find a given class.  This method is getting called for every non-injected field of a conversational component, on every invocation of a method in that component.  In my case, getEjbDescriptor  was eating up an average of 20% of page time before the attached patch.

-- 
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

        



More information about the seam-issues mailing list