You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Shammy Chen (JIRA)" <ji...@apache.org> on 2009/02/20 10:01:07 UTC

[jira] Created: (ODE-525) Thread synchronization / block (eg. XML manipulation ) slows ODE down dramaticly

Thread synchronization / block (eg. XML manipulation ) slows ODE down dramaticly
--------------------------------------------------------------------------------

                 Key: ODE-525
                 URL: https://issues.apache.org/jira/browse/ODE-525
             Project: ODE
          Issue Type: Improvement
          Components: BPEL Runtime
    Affects Versions: 1.2
         Environment: ODE 1.2
JAVA 5.0+
            Reporter: Shammy Chen


Recently we've been profiling ODE by jProfiler and found thread synchronization block ODE and AXIS2 threads so much. 

For example,in our 16 minutes test,calss sun.misc.URLClassPath blocked 342282 times and amounted to 30648 seconds. Class net.sf.saxon.om.NamePool has similar problem, maybe there are other candidates.

I think, if we resolve thread synchronization problem, ODE can perform much better.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (ODE-525) Thread synchronization / block (eg. XML manipulation ) slows ODE down dramaticly

Posted by "Shammy Chen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/ODE-525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675616#action_12675616 ] 

Shammy Chen commented on ODE-525:
---------------------------------

The data was extracted from jProfiler result, since our test was multi-threaded, thread block time may collapse each other.

If you'd like to settle this, HelloWorld2 example running in memory mode will show you this behavior.

> Thread synchronization / block (eg. XML manipulation ) slows ODE down dramaticly
> --------------------------------------------------------------------------------
>
>                 Key: ODE-525
>                 URL: https://issues.apache.org/jira/browse/ODE-525
>             Project: ODE
>          Issue Type: Improvement
>          Components: BPEL Runtime
>    Affects Versions: 1.2
>         Environment: ODE 1.2
> JAVA 5.0+
>            Reporter: Shammy Chen
>
> Recently we've been profiling ODE by jProfiler and found thread synchronization block ODE and AXIS2 threads so much. 
> For example,in our 16 minutes test,calss sun.misc.URLClassPath blocked 342282 times and amounted to 30648 seconds. Class net.sf.saxon.om.NamePool has similar problem, maybe there are other candidates.
> I think, if we resolve thread synchronization problem, ODE can perform much better.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (ODE-525) Thread synchronization / block (eg. XML manipulation ) slows ODE down dramaticly

Posted by "Alexis Midon (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/ODE-525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexis Midon updated ODE-525:
-----------------------------

    Fix Version/s: Wishlist

> Thread synchronization / block (eg. XML manipulation ) slows ODE down dramaticly
> --------------------------------------------------------------------------------
>
>                 Key: ODE-525
>                 URL: https://issues.apache.org/jira/browse/ODE-525
>             Project: ODE
>          Issue Type: Improvement
>          Components: BPEL Runtime
>    Affects Versions: 1.2
>         Environment: ODE 1.2
> JAVA 5.0+
>            Reporter: Shammy Chen
>             Fix For: Wishlist
>
>
> Recently we've been profiling ODE by jProfiler and found thread synchronization block ODE and AXIS2 threads so much. 
> For example,in our 16 minutes test,calss sun.misc.URLClassPath blocked 342282 times and amounted to 30648 seconds. Class net.sf.saxon.om.NamePool has similar problem, maybe there are other candidates.
> I think, if we resolve thread synchronization problem, ODE can perform much better.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (ODE-525) Thread synchronization / block (eg. XML manipulation ) slows ODE down dramaticly

Posted by "Mateusz Nowakowski (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/ODE-525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12759062#action_12759062 ] 

Mateusz Nowakowski commented on ODE-525:
----------------------------------------

I've found the same during JProfiling and YourKit profiling.
I've profiled ODE inside ServiceMix (Fuse to be more precise) 
and saw that the ODE threads are blocked most of the time on net.sf.saxon.om.NamePool monitor.

I can't provide you precise data, but about 90% blocked time was on this monitor on both Java profilers.

The issue is that how Saxon is used in ODE.
ODE 1.2 uses Saxon in 8.7 version and I googled that it is possible to provide new NamePool object to each xPath evaluation. This causes that threads are no longer blocked on this monitor.

Hovewer the issue may be solved inside Saxon library in 9.x, but I haven't tested it yet, because there are no working ServiceMix ODE 1.3.x release.
I'll try to find time to test it against 1.3.4-SNAPSHOT and figure it out if the issue still occurs.

> Thread synchronization / block (eg. XML manipulation ) slows ODE down dramaticly
> --------------------------------------------------------------------------------
>
>                 Key: ODE-525
>                 URL: https://issues.apache.org/jira/browse/ODE-525
>             Project: ODE
>          Issue Type: Improvement
>          Components: BPEL Runtime
>    Affects Versions: 1.2
>         Environment: ODE 1.2
> JAVA 5.0+
>            Reporter: Shammy Chen
>
> Recently we've been profiling ODE by jProfiler and found thread synchronization block ODE and AXIS2 threads so much. 
> For example,in our 16 minutes test,calss sun.misc.URLClassPath blocked 342282 times and amounted to 30648 seconds. Class net.sf.saxon.om.NamePool has similar problem, maybe there are other candidates.
> I think, if we resolve thread synchronization problem, ODE can perform much better.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (ODE-525) Thread synchronization / block (eg. XML manipulation ) slows ODE down dramaticly

Posted by "Alex Boisvert (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/ODE-525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675666#action_12675666 ] 

Alex Boisvert commented on ODE-525:
-----------------------------------

It still doesn't make the information useful nor actionable.

You're saying there's a synchronization issue but you don't provide any detail on the issue itself.  How is the synchronization preventing the system to achieve better performance?   Are there many other threads blocked by this synchronization?

There's also the fact that these classes are not in Ode itself, they are in 3rd party libraries... so either there are issues inside these libraries, or how we use them.  It would help to narrow down the issue to one of these two sides.

> Thread synchronization / block (eg. XML manipulation ) slows ODE down dramaticly
> --------------------------------------------------------------------------------
>
>                 Key: ODE-525
>                 URL: https://issues.apache.org/jira/browse/ODE-525
>             Project: ODE
>          Issue Type: Improvement
>          Components: BPEL Runtime
>    Affects Versions: 1.2
>         Environment: ODE 1.2
> JAVA 5.0+
>            Reporter: Shammy Chen
>
> Recently we've been profiling ODE by jProfiler and found thread synchronization block ODE and AXIS2 threads so much. 
> For example,in our 16 minutes test,calss sun.misc.URLClassPath blocked 342282 times and amounted to 30648 seconds. Class net.sf.saxon.om.NamePool has similar problem, maybe there are other candidates.
> I think, if we resolve thread synchronization problem, ODE can perform much better.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (ODE-525) Thread synchronization / block (eg. XML manipulation ) slows ODE down dramaticly

Posted by "Alex Boisvert (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/ODE-525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675427#action_12675427 ] 

Alex Boisvert commented on ODE-525:
-----------------------------------

Sorry, but the data you're providing is not very actionable and probably wrong as well.   (30648 seconds = 510 minutes???  In a 16 minutes test??)

We would need full stacktraces, and use-case that describes what the server is doing and under which circumstances, etc.

> Thread synchronization / block (eg. XML manipulation ) slows ODE down dramaticly
> --------------------------------------------------------------------------------
>
>                 Key: ODE-525
>                 URL: https://issues.apache.org/jira/browse/ODE-525
>             Project: ODE
>          Issue Type: Improvement
>          Components: BPEL Runtime
>    Affects Versions: 1.2
>         Environment: ODE 1.2
> JAVA 5.0+
>            Reporter: Shammy Chen
>
> Recently we've been profiling ODE by jProfiler and found thread synchronization block ODE and AXIS2 threads so much. 
> For example,in our 16 minutes test,calss sun.misc.URLClassPath blocked 342282 times and amounted to 30648 seconds. Class net.sf.saxon.om.NamePool has similar problem, maybe there are other candidates.
> I think, if we resolve thread synchronization problem, ODE can perform much better.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.