camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From salemi <sal...@avaya.com>
Subject Re: best practice for logging execution time
Date Tue, 30 Jul 2013 17:15:45 GMT
Claus,


I have to figure out how many messages we can put trough one Camel instance.
We need to at least manage to route 1000 messages a second.

Looking at the JMX stats I see each message takes about 10ms. I was
wondering how can Identify where the times are spent and how I can improve
my route!

What the route does is receive a messages from JMS topic convert it from
JSON String to a JSON Object and for send tto javaspaces. The javaspaces
right is a clusted write do the performance is bad. So I added a aggregator
in front of the javaspaces and now I am writing 10 messages at the time to
javaspaces. So the question how to measure the times from receiving the 10
messages received until they get written in javaspaces.  

<route>
<from uri="jms:topic:topic1">
<unmarshal ref="csJSON"/>
<to uri="direct:javaspaces"/>
<route>
  
<route id="javaspaces" shutdownRunningTask="CompleteCurrentTaskOnly"
autoStartup="true">
<from uri="direct:javaspaces"/>
<transacted/>
<aggregate strategyRef="aggregatorStrategy" completionSize="10"
completionTimeout="1000">
<correlationExpression>
<simple>${body.entity}</simple>
</correlationExpression>
<bean ref="jsInterface"/>
</aggregate>
</route>



-----
Alireza Salemi
--
View this message in context: http://camel.465427.n5.nabble.com/best-practice-for-logging-execution-time-tp2844045p5736506.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Mime
View raw message