[
https://issues.apache.org/jira/browse/XERCESJ-1573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13417768#comment-13417768
]
Jorge L. Williams commented on XERCESJ-1573:
--------------------------------------------
That certainly solves the memory problem. Looks like you're recreating the
XPath engine on startDocument? I'm wondering instead if you should be
resetting the engine -- if possible.
The performance difference is huge when you add assertions.
no assertions: good.xml: 78801/1000000=0.078801 ms
assertions: good.xml: 1171421/1000000=1.171421 ms
It took a little less than 2 mins to complete a million iterations on
duration-sans-assert.xsd (d7.png)
close to 20 mins on duration.xsd (d8.png).
I'm not seeing that sort of performance degradation with the saxon impl. Not
sure if that's related to this fix though -- I'll pop up a profiler to it when
I get a chance.
Thanks
> Possible memory leak when using assertions
> ------------------------------------------
>
> Key: XERCESJ-1573
> URL: https://issues.apache.org/jira/browse/XERCESJ-1573
> Project: Xerces2-J
> Issue Type: Bug
> Components: XML Schema 1.1 Datatypes
> Affects Versions: 2.11.0
> Reporter: Jorge L. Williams
> Priority: Blocker
> Attachments: XS11Validate.java, d1.png, d2.png, d3.png, d4.png,
> d5.png, d6.png, duration-sans-assert.xsd, duration.xsd, good.xml, mem.png
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
