You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Michael Dürig (JIRA)" <ji...@apache.org> on 2013/07/16 17:48:48 UTC

[jira] [Commented] (OAK-905) Performance issue with xml import

    [ https://issues.apache.org/jira/browse/OAK-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13709859#comment-13709859 ] 

Michael Dürig commented on OAK-905:
-----------------------------------

In a quick profiling session {{getNodeByIdentifier}} accounted for 93% of the time.
                
> Performance issue with xml import
> ---------------------------------
>
>                 Key: OAK-905
>                 URL: https://issues.apache.org/jira/browse/OAK-905
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>            Reporter: angela
>
> while playing around with the various access controlled related benchmarks from jackrabbit core, it shows that importing a huge content tree using xml-import is much slower on oak that it was on jackrabbit.
> initial numbers from the setup of the ReadDeepTreeTest which just reports how many ms it took to
> import the huge (deep) tree:
> jackrabbit:    31464 ms
> oak-default: 515106 ms
> oak-tar: 503543 ms
> i therefore decided to extract that import to a separate test class and commited org.apache.jackrabbit.oak.benchmark.XmlImportTest, which just imports the xml file during runTest()
> at revision 1503739.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira