[ 
https://issues.apache.org/jira/browse/CAMEL-3776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13244091#comment-13244091
 ] 

Frank Kootte edited comment on CAMEL-3776 at 4/2/12 10:20 AM:
--------------------------------------------------------------

The change I made was against tag/2.9.1 and I see you patched trunk ( makes 
more sense ). Question for us is at which request rate congestion will occur 
around the ReentrantLock compared to a pooled solution - which can scale on 
demand which is of our interest as we're dealing with quite the amount of 
requests per second on peak load. Load tests on the pooled impl I did provide a 
rough 300+ requests per second improvement showing no congestion until we 
consume 100% CPU resources. I am in the process of deploying a build of 
2.10-SNAPSHOT to perform the exact same test to see if and how the behavior 
between the 2 solutions differ when stressed.
                
      was (Author: frko):
    The change I made was against tag/2.9.1 and I see you patched trunk ( makes 
more sense ). I will checkout trunk and deploy a build to our load test 
environment.
                  
> Add pooling support for JAXB data format
> ----------------------------------------
>
>                 Key: CAMEL-3776
>                 URL: https://issues.apache.org/jira/browse/CAMEL-3776
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-jaxb
>            Reporter: Claus Ibsen
>             Fix For: 3.0.0
>
>         Attachments: jaxb-pool.patch
>
>
> We should use the ServicePool in camel-core to pool JAXB / marshaller / 
> unmarshaller.
> Of course ppl should be able to customize pool settings and if to be used.
> Also mind that for type converters with JAXB you do not configure a JAXB data 
> format. And thus we should
> still be able to configure and use pooling, so the type converter can be more 
> efficient.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to