svn commit: r1591874 - /jackrabbit/oak/trunk/oak-doc/src/site/markdown/dos_and_donts.md

[md...@apache.org]

Author: mduerig
Date: Fri May  2 11:36:12 2014
New Revision: 1591874

URL: http://svn.apache.org/r1591874
Log:
OAK-1455: document oak:unstructured performance advantages

Modified:
    jackrabbit/oak/trunk/oak-doc/src/site/markdown/dos_and_donts.md

Modified: jackrabbit/oak/trunk/oak-doc/src/site/markdown/dos_and_donts.md
URL: http://svn.apache.org/viewvc/jackrabbit/oak/trunk/oak-doc/src/site/markdown/dos_and_donts.md?rev=1591874&r1=1591873&r2=1591874&view=diff
==============================================================================
--- jackrabbit/oak/trunk/oak-doc/src/site/markdown/dos_and_donts.md (original)
+++ jackrabbit/oak/trunk/oak-doc/src/site/markdown/dos_and_donts.md Fri May  2 11:36:12 2014
@@ -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