jackrabbit-oak-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mdue...@apache.org
Subject svn commit: r1593055 - in /jackrabbit/oak/branches/1.0: ./ oak-doc/ oak-doc/src/site/markdown/dos_and_donts.md
Date Wed, 07 May 2014 16:26:11 GMT
Author: mduerig
Date: Wed May  7 16:26:10 2014
New Revision: 1593055

URL: http://svn.apache.org/r1593055
OAK-301: Document Oak
Merged r1591874

    jackrabbit/oak/branches/1.0/   (props changed)
    jackrabbit/oak/branches/1.0/oak-doc/   (props changed)

Propchange: jackrabbit/oak/branches/1.0/
  Merged /jackrabbit/oak/trunk:r1591874

Propchange: jackrabbit/oak/branches/1.0/oak-doc/
  Merged /jackrabbit/oak/trunk/oak-doc:r1591874

Modified: jackrabbit/oak/branches/1.0/oak-doc/src/site/markdown/dos_and_donts.md
URL: http://svn.apache.org/viewvc/jackrabbit/oak/branches/1.0/oak-doc/src/site/markdown/dos_and_donts.md?rev=1593055&r1=1593054&r2=1593055&view=diff
--- jackrabbit/oak/branches/1.0/oak-doc/src/site/markdown/dos_and_donts.md (original)
+++ jackrabbit/oak/branches/1.0/oak-doc/src/site/markdown/dos_and_donts.md Wed May  7 16:26:10
@@ -45,3 +45,11 @@ across threads. Don't access the same se
 multiple threads. When doing so Oak will protect its internal data structures
 from becoming corrupted but will not make any guarantees beyond that. In
 particular violating clients might suffer from lock contentions or deadlocks.
+### Large number of direct child node
+Oak scales to large number of direct child nodes of a node as long as those
+are *not* orderable. For orderable child nodes Oak keeps the order in an
+internal property, which will lead to a performance degradation when the list
+grows too large. For such scenarios Oak provides the ``oak:Unstructured`` node
+type, which is equivalent to ``nt:unstructured`` except that it is not orderable.
\ No newline at end of file

View raw message