[
https://issues.apache.org/jira/browse/ODE-876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12891255#action_12891255
]
Rafal Rusin commented on ODE-876:
---------------------------------
I know you can't provide. However I don't think there's other way than you to
prepare test case, which is slow and then we can work on it. You can use ping
pong example
(https://svn.apache.org/repos/asf/ode/trunk/distro/src/examples-jbi/maven2/ping-pong/).
> ODE 1.3.4 is 10 times slower than ODE 1.2
> -----------------------------------------
>
> Key: ODE-876
> URL: https://issues.apache.org/jira/browse/ODE-876
> Project: ODE
> Issue Type: Bug
> Components: JBI Integration
> Affects Versions: 1.3.4
> Environment: ODE 1.3.4 JBI, Fuse 3.4.0.5, ODE database in memory
> Reporter: Mateusz Nowakowski
> Priority: Blocker
> Fix For: 1.4
>
>
> We've recently migrated from ODE 1.2 JBI to ODE 1.3.4 JBI.
> We were unable to migrate earlier due to criticial bugs in JBI packages in
> 1.3.3 and 1.3.2..
> We ran the same performance test against new ODE 1.3.4 and previous ODE 1.2
> The same configuration, the same environment, the same test case, only
> different ODE zip...
> For example:
> A service which has about 7 invokes bpel activities with ODE 1.3.4 spends on
> processing 5500 ms
> with ODE 1.2 600ms.. The timings spend on these 7 services doesn't change.
> JBI bus time doesn;t change. Nothing has changed except ODE version.
> It happens the same for our all orchestrated services.
> The only thing which was changed is ODE version.
> I can't provide the test itself (prioprietary) but I can provide
> configuration.
> Our services are only in memory.
> ODE database is JBI external and it is Derby in memory.
> However the results are shocking. We of course abandon ODE 1.3.4 ans stay
> with ODE 1.2, but if it is not fixed, we may abandon ODE completely.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
