[
https://issues.apache.org/jira/browse/CAMEL-5918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-5918:
-------------------------------
Issue Type: New Feature (was: Improvement)
> Add performance tests
> ---------------------
>
> Key: CAMEL-5918
> URL: https://issues.apache.org/jira/browse/CAMEL-5918
> Project: Camel
> Issue Type: New Feature
> Components: camel-test
> Affects Versions: 2.9.5, 2.10.3
> Reporter: Christian Müller
> Assignee: Christian Müller
> Fix For: 2.8.7, 2.9.6, 2.10.4, 2.11.0
>
>
> By working on the "ESB Performance Testing - Round 7"
> (http://www.esbperformance.org/) to provide a good/optimal ServiceMix & Camel
> test set up I figured out, the performance for most of the test cases are
> worse by upgrading from ServiceMix 4.4.2 (which use Camel 2.8.5) to
> ServiceMix 4.5.0-SNAPSHOT (which use Camel 2.10.3).
> The reason for this does not have to be a worse performance in Camel, but it
> could. In these performance tests, I use ServiceMix/Karaf, Jetty, CXF, ...
> and Camel of course.
> To make sure the performance is not getting worse in a new Camel release, I
> will add a few different performance test in the next days/weeks for the most
> relevant use cases and the tests made by esbperformance.org. These test
> should not be executed by default on the CI server. But we should run the
> tests regularly from time to time and before we cut a new release. We also
> can use these tests to profile Camel and check we can improve the
> performance, independently how good the performance already is.
> I'm wondering what is the best place for this module. I suggest
> camel/tests/camel-performance. I don't know what the intension was for the
> existing camel/tests/camel-itest-performance module? It doesn't contain
> performance tests...
--
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
