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] Updated: (ODE-876) ODE 1.3.4 is 10 times slower than ODE 1.2
Date Thu, 18 Nov 2010 16:23:15 GMT

     [ https://issues.apache.org/jira/browse/ODE-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Mateusz Nowakowski updated ODE-876:

    Attachment: ODE_performanceComparison.pdf


We have finally some time and resources to work on that. (limited of course)

First of all we did two thinks:
1) retest it in different environment, with small amount of required TPS to check how big
traffic is required to make it visible;

Test plan and results attached.

It is seen even with 5TPS.
For 10 TPS the response time is 8-10 times bigger for ODE 1.3.4. So it doesn't require big
CPU utilization is bigger 5-10 %
Memory utilization 2-3 time bigger (measured as the amount of FullGCs)

2)  Fallback Saxon, 
It is not easy as expected, after fallback the processes don't work.

Our plan is to:
1) run some Java profilers
2) static code analysis.. it can be tough
3) write some project from scratch under Fuse/SMX3 and give you as an example.

> 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, ODE database in memory
>            Reporter: Mateusz Nowakowski
>            Assignee: Rafal Rusin
>            Priority: Blocker
>             Fix For: 1.4
>         Attachments: ODE_performanceComparison.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