You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@camel.apache.org by "Eric (JIRA)" <ji...@apache.org> on 2013/06/24 17:21:20 UTC

[jira] [Updated] (CAMEL-6485) Performance improvement in DefaultCamelContext by delaying synchronized block

     [ https://issues.apache.org/jira/browse/CAMEL-6485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eric updated CAMEL-6485:
------------------------

    Attachment: defaultcamelcontext.patch
    
> Performance improvement in DefaultCamelContext by delaying synchronized block
> -----------------------------------------------------------------------------
>
>                 Key: CAMEL-6485
>                 URL: https://issues.apache.org/jira/browse/CAMEL-6485
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 2.11.0
>            Reporter: Eric
>              Labels: performance
>         Attachments: defaultcamelcontext.patch
>
>
> When using Camel in a hi-throughput/multithreaded environment, I see a lot of contention in the DefaultCamelContext.getManagementStrategy() method.  Camel is synchronizing on an AtomicBoolean no matter what is the value of the boolean.  It is only required if the managementStrategy has not been initialized yet.  I have attached a patch that delays the synchronization to when the managementStrategy is not initialized.  This dramatically improved the performance of my system.

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