[jboss-jira] [JBoss JIRA] (AS7-6583) Performance regression comparing to previous release

[jaikiran pai (JIRA)]

    [ https://issues.jboss.org/browse/AS7-6583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12756052#comment-12756052 ] 

jaikiran pai commented on AS7-6583:
-----------------------------------

The https://github.com/jboss-logging/jboss-logmanager/blob/master/src/main/java/org/jboss/logmanager/ClassLoaderLogContextSelector.java#L78 can indeed turn out to be expensive since it scans the stacktrace elements to check for the calling classes to see if any of those classloaders have a LogContext associated with it. I'm not too sure why we need to find a LogContext in such a fashion instead of relying on TCCL (which is what ContextClassLoaderLogContextSelector did). Maybe James knows.

                
> Performance regression comparing to previous release
> ----------------------------------------------------
>
>                 Key: AS7-6583
>                 URL: https://issues.jboss.org/browse/AS7-6583
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: CDI / Weld, Logging
>    Affects Versions: 7.2.0.Alpha1
>         Environment: 7.2.0.Final (prerelease-1 tag) 
>            Reporter: Tomas Remes
>            Assignee: James Perkins
>            Priority: Critical
>              Labels: performance
>         Attachments: AS7-snapshot-good.jps, AS7-snapshot-wrong.jps
>
>
> There is significant performance regression in 7.2.0 prerelease. I discovered it in my Weld performance load tests (testing simple Weld numberguess example application), but I am quite sure that's not Weld issue at all. I did some investigations and it seems that problem occurred in org/jboss/as/logging module.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira