1
0
mirror of https://github.com/minio/docs.git synced 2025-07-31 18:04:52 +03:00

Move thresholds page and add references (#1020)

Per a request from @klauspost, this moves the Thresholds and Limits page
to a more logical place as a core operational concept.

Closes #1018 .
This commit is contained in:
Daryl White
2023-10-06 16:56:21 -04:00
committed by GitHub
parent 07d94a4aa7
commit 5c766a8008
3 changed files with 1 additions and 1 deletions

View File

@ -70,6 +70,7 @@ Clients therefore drive the overall hierarchy of data within a given bucket or p
MinIO has no hard :ref:`thresholds <minio-server-limits>` on the number of buckets, objects, or prefixes on a given deployment.
The relative performance of the hardware and networking underlying the MinIO deployment may create a practical limit to the number of objects in a given prefix or bucket.
Specifically, hardware using slower drives or network infrastructures tend to exhibit poor performance in buckets or prefixes with a flat hierarchy of objects.
For other considerations, thresholds, or limitations to keep in mind, see :ref:`minio-server-limits`.
Consider the following points as general guidance for client applications workload patterns:

View File

@ -23,7 +23,6 @@ Checklists:
- :ref:`Hardware Checklist <minio-hardware-checklist>`
- :ref:`Security Checklist <minio-security-checklist>`
- :ref:`Software Checklist <minio-software-checklists>`
- :ref:`Thresholds and Limits <minio-server-limits>`
.. toctree::
:titlesonly: