Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Mon, 7 Jan 2013 11:28:12 +0000 (UTC)
From: "Claus Ibsen (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <JIRA.12625482.1356785783090.89850.1357558092552@arcas>
In-Reply-To: <JIRA.12625482.1356785783090@arcas>
References: <JIRA.12625482.1356785783090@arcas>
Subject: [jira] [Updated] (CAMEL-5918) Add performance tests
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/CAMEL-5918?page=3Dcom.atlassia=
n.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen updated CAMEL-5918:
-------------------------------

    Issue Type: New Feature  (was: Improvement)
   =20
> 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=C3=BCller
>            Assignee: Christian M=C3=BCller
>             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.esbperf=
ormance.org/) to provide a good/optimal ServiceMix & Camel test set up I fi=
gured out, the performance for most of the test cases are worse by upgradin=
g from ServiceMix 4.4.2 (which use Camel 2.8.5) to ServiceMix 4.5.0-SNAPSHO=
T (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 te=
st should not be executed by default on the CI server. But we should run th=
e tests regularly from time to time and before we cut a new release. We als=
o can use these tests to profile Camel and check we can improve the perform=
ance, independently how good the performance already is.
> I'm wondering what is the best place for this module. I suggest camel/tes=
ts/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 administrato=
rs
For more information on JIRA, see: http://www.atlassian.com/software/jira