[
https://issues.apache.org/jira/browse/ODE-876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12891324#action_12891324
]
Mateusz Nowakowski commented on ODE-876:
----------------------------------------
The PingPong is a nice startup point to provide the example. So I'll try but it
may take some time.
The main difference between PingPong and my services is that my services
invokes a XSL2 transformations before and after invoke. The payloads are bigger
than in PingPong, for example 20 KB.
What is more each invoke takes about 50-100ms to process so it may have impact
on thread scheduling.
GC parameters are fixed (for young and old gen) however it may change during
the test but not significantly, because gc full scans are rare.
I do not have Saxon on global SMX classpath so ODE uses own Saxon from own
service engine. Saxon version has changed, so it may be this.
I'll repeat the test with old Saxon and let you know.
> 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
> Assignee: Rafal Rusin
> Priority: Blocker
> Fix For: 1.4
>
> Attachments: 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.
