[jboss-jira] [JBoss JIRA] Commented: (BPEL-310) Performance improvement: switch from Jaxen to a different XPath engine (e.g. Resin)

Fri Oct 9 12:44:05 EDT 2009

    [ https://jira.jboss.org/jira/browse/BPEL-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12489203#action_12489203 ] 

Aleksander Adamowski commented on BPEL-310:
-------------------------------------------

BTW, Jaxen processing seems to really be a bottleneck in jBPM-BPEL now (after fixing BPEL-309).

Under the profiler, we can see that the biggest hot spots are:

org.jaxen.expr.DefaultNameStep.matches()
org.jaxen.expr.DefaultNameStep.evaluate()
org.jaxen.dom.DocumentNavigator.getParentNode()
org.jaxen.dom.DocumentNavigator.isElement()

and some other methods in org.jaxen.expr.DefaultVariableReferenceExpr and org.jaxen.expr.DefaultFunctionCallExpr.

Of course, this depends on the particular BPEL definition's XML document.

> Performance improvement: switch from Jaxen to a different XPath engine (e.g. Resin)
> -----------------------------------------------------------------------------------
>
>                 Key: BPEL-310
>                 URL: https://jira.jboss.org/jira/browse/BPEL-310
>             Project: jBPM BPEL
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: jBPM BPEL 1.1.1
>            Reporter: Aleksander Adamowski
>            Assignee: Alejandro Guizar
>            Priority: Optional
>
> According to this benchmark, Jaxen is the slowest of all available XPath engines:
> http://www.asciiarmor.com/post/33736620/java-xpath-1-0-engine-comparison-performance
> It would probably be a nice idea to switch to any other XPath engine, but preferably to Caucho Resin's one since it's the fastest (see the benchmark). It would probably also make the licensing issues more clear, as Jaxen has a non-standard open source license, while Resin is GPL.
> However, one must take into account various incompatibilities present in those engines at the moment the benchmark was performed (relevant bugs were filed, but it's to be verified whether they were really fixed):
> http://www.asciiarmor.com/post/33736618/java-xpath-1-0-engine-comparison-compliance

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira