ode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mateusz Nowakowski (JIRA)" <j...@apache.org>
Subject [jira] Commented: (ODE-876) ODE 1.3.4 is 10 times slower than ODE 1.3.3
Date Tue, 23 Nov 2010 15:48:14 GMT

    [ https://issues.apache.org/jira/browse/ODE-876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12934862#action_12934862

Mateusz Nowakowski commented on ODE-876:

>Are there other issues that have been fixed in trunk that should go into 1.3.5?
To be honest, we didn't search other bottlenecks. We've found it, fixed it and tested. The
results are similar to ODE 1.2, even slightly better than 1.2, so we stopped further testing,
because the results are acceptable for us.

>Are there other issues that have been fixed in trunk that should go into 1.3.5? 
To be honest, we spent some time to make sure that 1.3.4 is compatible with 1.2 for functional
point of view for our existing processes.
Now we are almost sure that from performance point of view it works similarly, so we don't
want revolutionary changes in 1.3.5.

The previous three releases of JBI ODE didn't work for us (for example JIRAS: ODE-603, ODE-604,
ODE-605, ODE-651, ODE-806, ODE-840 and now ODE-876), so we are still on ODE 1.2 and now we
are extremely cautious. 

When you are ready to release 1.3.5, please release it as RC, freeze the code, so that we
will have about 2 weeks to verify that it works for us.
We need to perform some bigger, "official" tests and we have to find "free" slots for that.

> ODE 1.3.4 is 10 times slower than ODE 1.3.3
> -------------------------------------------
>                 Key: ODE-876
>                 URL: https://issues.apache.org/jira/browse/ODE-876
>             Project: ODE
>          Issue Type: Bug
>          Components: BPEL Runtime
>    Affects Versions: 1.3.3
>         Environment: ODE 1.3.4 JBI, Fuse, ODE database in memory
>            Reporter: Mateusz Nowakowski
>            Assignee: Rafal Rusin
>            Priority: Blocker
>             Fix For: 1.3.5
>         Attachments: ODE_performanceComparison.pdf, OdeProfiling.pdf, ping-pong-load-test-soapui-project.xml,
> 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
> 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
> 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.

View raw message