You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by marioradev <ma...@softwareag.com> on 2013/10/24 14:40:24 UTC
Performance degradation on consumer side when switching Camel from
2.11.0 to 2.12.1v
Hi there.
Last week we have switched our product to use Apache Camel 2.12.1 version
instead of 2.11.0 version. On one of our performance tests we have detected
degradation of 20% on the consumer side. The affected test case is when the
message is being created once and then sent/emitted N times. The publish
rate is OK, the subscription rate is about 20% lower compared to earlier
builds. When only switching back to use camel 2.11 results are as expected.
Are there any modifications done in this direction? Do you know is there
some issue already registered into the tracking system regarding this
problem? If there is do you know in which version this is going to be
solved?
Mario.
--
View this message in context: http://camel.465427.n5.nabble.com/Performance-degradation-on-consumer-side-when-switching-Camel-from-2-11-0-to-2-12-1v-tp5742125.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Performance degradation on consumer side when switching Camel
from 2.11.0 to 2.12.1v
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
I have logged a ticket to improve this
https://issues.apache.org/jira/browse/CAMEL-7203
On Tue, Feb 11, 2014 at 2:19 PM, Rosen Spasov <ro...@hotmail.com> wrote:
> It seems the performance regression is caused by a change triggered due to
> this defect: CAMEL-6541 <https://issues.apache.org/jira/browse/CAMEL-6541>
> . The excessive copy of message headers seems to be causing ~10%
> degradation. Any ideas how to overcome this?
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/Performance-degradation-on-consumer-side-when-switching-Camel-from-2-11-0-to-2-12-1v-tp5742125p5747114.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cibsen@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
Make your Camel applications look hawt, try: http://hawt.io
Re: Performance degradation on consumer side when switching Camel
from 2.11.0 to 2.12.1v
Posted by Rosen Spasov <ro...@hotmail.com>.
It seems the performance regression is caused by a change triggered due to
this defect: CAMEL-6541 <https://issues.apache.org/jira/browse/CAMEL-6541>
. The excessive copy of message headers seems to be causing ~10%
degradation. Any ideas how to overcome this?
--
View this message in context: http://camel.465427.n5.nabble.com/Performance-degradation-on-consumer-side-when-switching-Camel-from-2-11-0-to-2-12-1v-tp5742125p5747114.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Performance degradation on consumer side when switching Camel
from 2.11.0 to 2.12.1v
Posted by marioradev <ma...@softwareag.com>.
Thanks for the prompt reply. I am going to attach a project that could
reproduce the degradation. Will need some time to do such project and
isolate it from our current scenario.
Regards, Mario.
--
View this message in context: http://camel.465427.n5.nabble.com/Performance-degradation-on-consumer-side-when-switching-Camel-from-2-11-0-to-2-12-1v-tp5742125p5742395.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Performance degradation on consumer side when switching Camel
from 2.11.0 to 2.12.1v
Posted by Raul Kripalani <ra...@evosent.com>.
Hello,
The code base of the camel-jms component hasn't varied considerably [1] and
I don't outright see any cause why this component would be the culprit of
the slowdown.
I did spot a change in the JmsHeaderFilterStrategy to introduce the
includeAllJMSXProperties option. But this defaults to false, meaning that
the newly introduced logic is disabled anyway unless you explicitly enable
it. So I doubt this has anything to do.
I guess the performance regression could be elsewhere, i.e. camel-core.
Perhaps new Type Converters or the like? What kind of payload are you
dealing with?
In a nutshell, we'd have to profile to dig deeper into this. Could you
attach your project - watered down or obscured if need be - so I can
profile it against Camel 2.11 and 2.12.1 to identify where the hotspot is?
[1] git diff camel-2.11.0 camel-2.12.0 -- components/camel-jms
Thanks for the report,
*Raúl Kripalani*
Apache Camel PMC Member & Committer | Enterprise Architect, Open Source
Integration specialist
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk
On Thu, Oct 24, 2013 at 1:40 PM, marioradev <ma...@softwareag.com>wrote:
> Hi there.
>
> Last week we have switched our product to use Apache Camel 2.12.1 version
> instead of 2.11.0 version. On one of our performance tests we have detected
> degradation of 20% on the consumer side. The affected test case is when the
> message is being created once and then sent/emitted N times. The publish
> rate is OK, the subscription rate is about 20% lower compared to earlier
> builds. When only switching back to use camel 2.11 results are as expected.
> Are there any modifications done in this direction? Do you know is there
> some issue already registered into the tracking system regarding this
> problem? If there is do you know in which version this is going to be
> solved?
>
> Mario.
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Performance-degradation-on-consumer-side-when-switching-Camel-from-2-11-0-to-2-12-1v-tp5742125.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
Re: Performance degradation on consumer side when switching Camel
from 2.11.0 to 2.12.1v
Posted by marioradev <ma...@softwareag.com>.
Hi,
More details about the scenario. We are creating message only once and sent
it 500000 times. We have an emitter which route is configured from a vm
channel to JMS topic. Consumer is receiving messages from this JMS topic.
In the original test, emitting is configured with concurrentConsumers=30. To
isolate from where the problem may come from we have switched this property
to 1, but the degradation is the same - 20%. So seems that the reason is not
related with changes in this direction.
--
View this message in context: http://camel.465427.n5.nabble.com/Performance-degradation-on-consumer-side-when-switching-Camel-from-2-11-0-to-2-12-1v-tp5742125p5742317.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Performance degradation on consumer side when switching Camel
from 2.11.0 to 2.12.1v
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
You should tell more about your Camel application, as Camel has 100s
of components so not sure which you use etc, that can possible cause a
slowdown in your situation.
On Thu, Oct 24, 2013 at 2:40 PM, marioradev <ma...@softwareag.com> wrote:
> Hi there.
>
> Last week we have switched our product to use Apache Camel 2.12.1 version
> instead of 2.11.0 version. On one of our performance tests we have detected
> degradation of 20% on the consumer side. The affected test case is when the
> message is being created once and then sent/emitted N times. The publish
> rate is OK, the subscription rate is about 20% lower compared to earlier
> builds. When only switching back to use camel 2.11 results are as expected.
> Are there any modifications done in this direction? Do you know is there
> some issue already registered into the tracking system regarding this
> problem? If there is do you know in which version this is going to be
> solved?
>
> Mario.
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/Performance-degradation-on-consumer-side-when-switching-Camel-from-2-11-0-to-2-12-1v-tp5742125.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cibsen@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen