You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Mateusz Nowakowski (JIRA)" <ji...@apache.org> on 2010/07/22 11:58:50 UTC
[jira] Created: (ODE-876) ODE 1.3.4 is 10 times slower than ODE 1.2
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.
[jira] Commented: (ODE-876) ODE 1.3.4 is 10 times slower than ODE
1.2
Posted by "Rafal Rusin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12891087#action_12891087 ]
Rafal Rusin commented on ODE-876:
---------------------------------
Please provide sample process and soapui load test, so we can check it out.
Regards
> 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.
[jira] Commented: (ODE-876) ODE 1.3.4 is 10 times slower than ODE
1.2
Posted by "Rafal Rusin (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (ODE-876) ODE 1.3.4 is 10 times slower than ODE 1.2
Posted by "Rafal Rusin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rafal Rusin updated ODE-876:
----------------------------
Attachment: ping-pong-sa-1.0.0.zip
ping-pong-load-test-soapui-project.xml
I did performance comparison for ODE 1.2 and 1.3.4 JBI for 18 invokes (communication between ping and pong is over EIP - Seda Queue).
Test was run on 10 thread.
Please note that test case needs to be run twice, because JVM optimizes some functions and TPS grows.
Results are:
ODE 1.2: 11.33 TPS
ODE 1.3.4: 10.82 TPS
So performance drop is around 5%.
That's why I need a particular test case.
Regards
> 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
>
> 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.
[jira] Assigned: (ODE-876) ODE 1.3.4 is 10 times slower than ODE
1.2
Posted by "Rafal Rusin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rafal Rusin reassigned ODE-876:
-------------------------------
Assignee: Rafal Rusin
> 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.
[jira] Commented: (ODE-876) ODE 1.3.4 is 10 times slower than ODE
1.2
Posted by "Mateusz Nowakowski (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12891093#action_12891093 ]
Mateusz Nowakowski commented on ODE-876:
----------------------------------------
As I said I can't provide the test or process, because it is JBI based, so I would have to provide all JBI endpoints as well.
Is there any example of any load test (process and soapui test) in ODE JBI distibution?
It is so visible, so any load test should prove that.
> 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.
[jira] Commented: (ODE-876) ODE 1.3.4 is 10 times slower than ODE
1.2
Posted by "Mateusz Nowakowski (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Issue Comment Edited: (ODE-876) ODE 1.3.4 is 10 times slower
than ODE 1.2
Posted by "Rafal Rusin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12891292#action_12891292 ]
Rafal Rusin edited comment on ODE-876 at 7/22/10 3:37 PM:
----------------------------------------------------------
I did performance comparison for ODE 1.2 and 1.3.4 JBI for 18 invokes (communication between ping and pong is over EIP - Seda Queue).
Test was run on 10 threads.
Please note that test case needs to be run twice, because JVM optimizes some functions and TPS grows.
Results are:
ODE 1.2: 11.33 TPS
ODE 1.3.4: 10.82 TPS
So performance drop is around 5%.
That's why I need a particular test case.
Regards
was (Author: rrusin):
I did performance comparison for ODE 1.2 and 1.3.4 JBI for 18 invokes (communication between ping and pong is over EIP - Seda Queue).
Test was run on 10 thread.
Please note that test case needs to be run twice, because JVM optimizes some functions and TPS grows.
Results are:
ODE 1.2: 11.33 TPS
ODE 1.3.4: 10.82 TPS
So performance drop is around 5%.
That's why I need a particular test case.
Regards
> 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.