[
https://issues.apache.org/jira/browse/OAK-1312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15384191#comment-15384191
]
Felix Meschberger edited comment on OAK-1312 at 7/19/16 2:13 PM:
-----------------------------------------------------------------
I think this can be started with very simple and get quick successes: Just
bundle subtrees off of the jcr:content into the same document. No need for
massive type checking and analysis. Just a single piece in the path. Quick,
dirty, effective.
Background: Over the years it turns out that most nodes that have some form of
content, such as "Documents", CMS "Pages", files (nt:file for that matter !),
all have a jcr:content node to base this content off.
was (Author: fmeschbe):
I think this can be started with very simple and get quick successes: Just
bundle subtrees off of the jcr:content into the same document. No need for
massive type checking and analysis. Just a single piece in the path. Quick,
dirty, effective.
Background: Over the year it turns out that most nodes that have some form of
content, such as "Documents", CMS "Pages", files (nt:file for that matter !),
all have a jcr:content node to base this content off.
> Bundle nodes into a document
> ----------------------------
>
> Key: OAK-1312
> URL: https://issues.apache.org/jira/browse/OAK-1312
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: core, documentmk
> Reporter: Marcel Reutegger
> Assignee: Chetan Mehrotra
> Labels: performance
> Fix For: 1.6
>
>
> For very fine grained content with many nodes and only few properties per
> node it would be more efficient to bundle multiple nodes into a single
> MongoDB document. Mostly reading would benefit because there are less
> roundtrips to the backend. At the same time storage footprint would be lower
> because metadata overhead is per document.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
