camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <>
Subject Re: ESB Performance Testing - Round 6
Date Wed, 29 Aug 2012 07:11:06 GMT
On Tue, Aug 28, 2012 at 11:07 PM, Christian Müller
<> wrote:
> You may know the last ESB performance test results from round 6 [1].
> As you can see, Apache ServiceMix 4.3.0 failed to complete this benchmark.
> These tests are still based on the deprecated Apache ServiceMix JBI
> components.

First of all I think this test is single eye-sided on the area that
the people behind the tests,
is the areas where their solution is as its bests = only WS. And its
not a general purpose tests to show
all areas of the ESB. eg its only webservice based!

> Because of this, I implemented the required tests for Apache ServiceMix
> 4.4.2 and Apache Camel (2.8.5) - instead of using JBI. I hope we can pass
> the tests this time...

I guess when the time comes it makes sense to use SMX 4.5.0 with Camel
2.10.x and CXF 2.6.x to get the latest stuff.
Especially since both Camel and CXF in these releases have been
improved in the streaming areas of XML / CXF stuff.
I am not sure though how much this applies to the tests where you run
in MESSAGE mode in camel-cxf.

> Feel free to provide any feedback. May you find places where we can make

As the tests uses big/medium payloads 50kb, 100kb etc. and you have
enable stream caching in the code, then mind the default threshold for
spooling to disk is at 64kb limit. And when you spool to disk its
freaking slow compared to be kept in memory.
And its using the slow API and not any NIO memory mapped
files etc instead.

You can set an option to increase the threshold, to keep the messages in memory

Also I wonder if using OSGi blueprint would be better than the old
aging spring-dm 1.2.
And I guess the SMX can be trimmed down in size. Maybe with its
minimal configuration etc.
eg to drop all the legacy JBI and whatnot it carries by default.

> Apache ServiceMix and/or Apache Camel faster.
> You can find my Mercurial repo at [2] and my Git repo at [3].
> [1]
> [2]
> [3]
> Best,
> Christian
> --

Claus Ibsen
Twitter: davsclaus, fusenews
Author of Camel in Action:

View raw message