DOCS-14942 increase default chunk size (#221)

* DOCS-14942 increase default chunk size

* decreases font size

* resize

Author: jmd-mongo

source/core/sharding-data-partitioning.txt

@@ -97,7 +97,7 @@ Empty Collection
 Chunk Size
 ----------
 
-The default :term:`chunk` size in MongoDB is 64 megabytes. You can
+The default :term:`chunk` size in MongoDB is 128 megabytes. You can
 :doc:`increase or reduce the chunk size
 </tutorial/modify-chunk-size-in-sharded-cluster>`. Consider the
 implications of changing the default chunk size:

source/faq/diagnostics.txt

@@ -151,7 +151,7 @@ The two most important factors in maintaining a successful sharded cluster are:
 
 While you can :ref:`change your shard key <change-a-shard-key>` later,
 it is important to carefully consider your shard key choice to avoid
-scalability and perfomance issues. Continue reading for specific issues
+scalability and performance issues. Continue reading for specific issues
 you may encounter in a production environment.
 
 .. _sharding-troubleshooting-not-splitting:
@@ -163,15 +163,15 @@ Your cluster must have sufficient data for sharding to make
 sense. Sharding works by migrating chunks between the shards until
 each shard has roughly the same number of chunks.
 
-The default chunk size is 64 megabytes. MongoDB will not begin
+The default chunk size is 128 megabytes. MongoDB will not begin
 migrations until the imbalance of chunks in the cluster exceeds the
 :ref:`migration threshold <sharding-migration-thresholds>`. This
 behavior helps prevent unnecessary chunk migrations, which can degrade
 the performance of your cluster as a whole.
 
 If you have just deployed a sharded cluster, make sure that you have
 enough data to make sharding effective. If you do not have sufficient
-data to create more than eight 64 megabyte chunks, then all data will
+data to create more than eight 128 megabyte chunks, then all data will
 remain on one shard. Either lower the :ref:`chunk size
 <sharding-chunk-size>` setting, or add more data to the cluster.
 

source/images/sharding-splitting.bakedsvg.svg

@@ -1,3 +1,3 @@
 .. figure:: /images/sharding-splitting.bakedsvg.svg
-   :alt: Diagram of a shard with a chunk that exceeds the default chunk size of 64 MB and triggers a split of the chunk into two chunks.
+   :alt: Diagram of a shard with a chunk that exceeds the default chunk size of 128 MB and triggers a split of the chunk into two chunks.
    :figwidth: 400px

source/images/sharding-splitting.rst

@@ -132,7 +132,7 @@ Glossary
       :term:`shard`. Chunk ranges are inclusive of the lower boundary
       and exclusive of the upper boundary. MongoDB splits chunks when
       they grow beyond the configured chunk size, which by default is
-      64 megabytes. MongoDB migrates chunks when a shard contains too
+      128 megabytes. MongoDB migrates chunks when a shard contains too
       many chunks of a collection relative to other shards. See
       :ref:`sharding-data-partitioning` and :ref:`sharding-balancing`.
 

source/images/sharding-splitting.svg

@@ -65,7 +65,7 @@ To see if the balancer process is active in your :term:`cluster
 Configure Default Chunk Size
 ----------------------------
 
-The default chunk size for a sharded cluster is 64 megabytes. In most
+The default chunk size for a sharded cluster is 128 megabytes. In most
 situations, the default size is appropriate for splitting and migrating
 chunks. For information on how chunk size affects deployments, see
 details, see :ref:`sharding-chunk-size`.

source/reference/glossary.txt

@@ -10,7 +10,7 @@ Modify Chunk Size in a Sharded Cluster
    :depth: 1
    :class: singlecol
 
-The default chunk size for a sharded cluster is 64 megabytes. This
+The default chunk size for a sharded cluster is 128 megabytes. This
 default chunk size works well for most deployments; however, if you
 notice that automatic migrations have more I/O than your hardware can
 handle, you may want to reduce the chunk size. For automatic splits and