[
https://issues.apache.org/jira/browse/OAK-1037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13777338#comment-13777338
]
Chetan Mehrotra edited comment on OAK-1037 at 9/25/13 10:40 AM:
----------------------------------------------------------------
+1 for having an Query ExecutionContext
Yes with recent changes done as part of OAK-1036 the call to
AbstractRoot#getRootState does not cost much so not much gain in doing away
with those calls. But it would good if various part of query execution are
pinned to same NodeState. Probably it might still provide gain when using Mongo
MK
was (Author: chetanm):
+1 for having an Query ExecutionContext
Yes with recent changes done as part of OAK-1036 the call to
AbstractRoot#getRootState does not cost much so not much gain in doing away
with those calls. But it would good if various part of query execution are
pinned to same NodeState.
> Improve performance of XmlImport
> --------------------------------
>
> Key: OAK-1037
> URL: https://issues.apache.org/jira/browse/OAK-1037
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: jcr
> Affects Versions: 0.9
> Reporter: Chetan Mehrotra
> Assignee: Chetan Mehrotra
> Attachments: jmc-oak-importxml-1.png, OAK-1037.patch
>
>
> The XmlImport benchmark [1] is running slow on Oak compared to Jackrabbit on
> various persistence backends
> {noformat}
> # XmlImportTest min 10% 50% 90% max N
> Oak-Tar 277901 277922 282454 288859 289186 10
> Oak-Mongo 362531 363342 382810 401213 401954 10
> Jackrabbit 11961 11969 12816 14158 14173 10
> {noformat}
> The performance here needs to be improved
> [1]
> https://svn.apache.org/repos/asf/jackrabbit/oak/trunk/oak-run/src/main/java/org/apache/jackrabbit/oak/benchmark/XmlImportTest.java
--
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
