DOCS-1101 BinData index storage

source/applications/optimization.txt

@@ -66,8 +66,9 @@ order, the direction of a single-key index does not matter.
 
 Indexes support queries, update operations, and some phases of the
 :ref:`aggregation pipeline
-<aggregation-pipeline-operators-and-performance>` for more
-information.
+<aggregation-pipeline-operators-and-performance>`.
+
+.. include:: /includes/fact-bindata-storage-optimization.rst
 
 Limit Results
 ~~~~~~~~~~~~~

source/core/document.txt

@@ -233,10 +233,11 @@ Consider the following options for the value of an ``_id`` field:
   :doc:`/tutorial/create-an-auto-incrementing-field` tutorial for an
   implementation pattern.
 
-- Generate a UUID in your application code. For efficiency, store
-  the UUID as a value of the BSON ``BinData`` type to reduce the
-  size of UUID values as stored in the collection and in the ``_id``
-  index.
+- Generate a UUID in your application code. For a more efficient
+  storage of the UUID values in the collection and in the ``_id``
+  index, store the UUID as a value of the BSON ``BinData`` type.
+
+  .. include:: /includes/fact-bindata-storage-optimization.rst
 
 - Use your driver's BSON UUID facility to generate UUIDs. Be aware
   that driver implementations may implement UUID serialization and

source/includes/fact-bindata-storage-optimization.rst

@@ -0,0 +1,7 @@
+Index keys that are of the ``BinData`` type are more efficiently stored
+in the index if:
+
+- the binary subtype value is in the range of 0-7 or 128-135, and
+
+- the length of the byte array is: 0, 1, 2, 3, 4, 5, 6, 7, 8, 10, 12,
+  14, 16, 20, 24, or 32.