camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CAMEL-6485) Performance improvement in DefaultCamelContext by delaying synchronized block
Date Tue, 25 Jun 2013 09:10:21 GMT

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

Claus Ibsen resolved CAMEL-6485.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 2.12.0
                   2.11.1
                   2.10.6

Backported the patch as I was backporting other stuff.

Eric, thanks for reporting and with the 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
>            Assignee: Willem Jiang
>              Labels: performance
>             Fix For: 2.10.6, 2.11.1, 2.12.0
>
>         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

Mime
View raw message