ode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tammo van Lessen (JIRA)" <j...@apache.org>
Subject [jira] Updated: (ODE-876) ODE 1.3.4 is 10 times slower than ODE 1.3.3
Date Thu, 02 Dec 2010 01:14:11 GMT

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

Tammo van Lessen updated ODE-876:
---------------------------------

    Attachment: ODE-876-2.patch

Hi Mateusz,

I've created a new patch with your suggestions. The XPathFactory is now a field so that the
configuration object is created only once per process model. Also I've added a couple of isDebugEnabled()
checks.

Could you please test it again? I think we're coming closer.

Thanks,
  Tammo

> 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 3.4.0.5, ODE database in memory
>            Reporter: Mateusz Nowakowski
>            Assignee: Tammo van Lessen
>            Priority: Blocker
>             Fix For: 1.3.5
>
>         Attachments: ODE-876-2.patch, ODE-876.patch, ODE1.3.4WithODEPath.pdf, ODE_performanceComparison.pdf,
OdeProfiling.pdf, ping-pong-load-test-soapui-project.xml, ping-pong-sa-1.0.0.zip
>
>
> 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.


Mime
View raw message