jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "angela (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-1312) Bundle nodes into a document
Date Tue, 19 Jul 2016 15:01:20 GMT

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

angela commented on OAK-1312:
-----------------------------

hm... but that particular example is pretty bad as someone might add the mixin just for the
sake of it and second it illustrates exactly how it should not be. the access control content
does not below to the document such as for example the jcr:content child node which is an
inherent part of the aggregate defined by a hierarchy node. the access control content belong
to a different dimension if you wish and if I had the option I would have written it to a
different 'storage' altogether :-)

> 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)

Mime
View raw message