mirror of
https://github.com/minio/docs.git
synced 2025-07-24 10:22:32 +03:00
Fix up recommendation page (#914)
This commit is contained in:
Ravind Kumar
GitHub
@ -26,18 +26,16 @@ When selecting hardware for your MinIO implementation, take into account the fol
|
||||
|
||||
.. _deploy-minio-distributed-recommendations:
|
||||
|
||||
Production Hardware Requirements
|
||||
--------------------------------
|
||||
Production Hardware Recommendations
|
||||
-----------------------------------
|
||||
|
||||
The following checklist provides a minimum hardware specification for production MinIO deployments.
|
||||
MinIO takes full advantage of the modern hardware improvements such as AVX-512 SIMD acceleration, 100GbE networking, and NVMe SSDs, when available.
|
||||
While MinIO can run on commodity or "budget" hardware, we strongly recommend using this table as guidance for best results in production environments.
|
||||
The following checklist follows MinIO's `Recommended Configuration <https://min.io/product/reference-hardware?ref-docs>`__ for production deployments.
|
||||
The provided guidance is intended as a baseline and cannot replace |subnet| Performance Diagnostics, Architecture Reviews, and direct-to-engineering support.
|
||||
|
||||
.. note::
|
||||
.. admonition:: MinIO does not provide hosted services or hardware sales
|
||||
:class: important
|
||||
|
||||
See our `Reference Hardware <https://min.io/product/reference-hardware?ref-docs>`__ page for a curated selection of servers and storage components from our hardware partners.
|
||||
|
||||
MinIO does not provide hosted services or hardware sales.
|
||||
See our `Reference Hardware <https://min.io/product/reference-hardware#hardware?ref-docs>`__ page for a curated selection of servers and storage components from our hardware partners.
|
||||
|
||||
.. list-table::
|
||||
:widths: auto
|
||||
@ -46,7 +44,7 @@ While MinIO can run on commodity or "budget" hardware, we strongly recommend usi
|
||||
* - :octicon:`circle`
|
||||
- Sufficient CPU cores to achieve performance goals for hashing (for example, for healing) and encryption
|
||||
|
||||
MinIO recommends Dual Intel® Xeon® Scalable Gold CPUs (minimum 16 cores per socket) or any CPU with AVX512 instructions
|
||||
MinIO recommends Single Socket Intel® Xeon® Scalable Gold CPUs (minimum 16 cores per socket).
|
||||
|
||||
* - :octicon:`circle`
|
||||
- Sufficient RAM to achieve performance goals based on the number of drives and anticipated concurrent requests (see the :ref:`formula and reference table <minio-hardware-checklist-memory>`).
|
||||
@ -54,16 +52,31 @@ While MinIO can run on commodity or "budget" hardware, we strongly recommend usi
|
||||
MinIO recommends a minimum of 128GB of memory per node for best performance.
|
||||
|
||||
* - :octicon:`circle`
|
||||
- Minimum of four nodes dedicated to object storage.
|
||||
- .. cond:: k8s
|
||||
|
||||
For containers or Kubernetes in virtualized environments, MinIO requires four distinct physical nodes.
|
||||
Colocating multiple high-performance softwares on the same nodes can result in resource contention and reduced overall performance.
|
||||
MinIO requires a *minimum* of 4 worker nodes per MinIO Tenant.
|
||||
|
||||
MinIO strongly recommends allocating worker nodes dedicated to servicing the MinIO Tenant.
|
||||
Colocating multiple high-performance services on the same nodes can result in resource contention and reduced overall performance.
|
||||
|
||||
.. cond:: linux or container or macos or windows
|
||||
|
||||
MinIO recommends a *minimum* of 4 host servers per distributed deployment.
|
||||
|
||||
MinIO strongly recommends hardware dedicated to servicing the MinIO Tenant.
|
||||
Colocating multiple high-performance services on the same servers can result in resource contention and reduced overall performance.
|
||||
|
||||
* - :octicon:`circle`
|
||||
- | SATA/SAS drives for balanced capacity-to-performance
|
||||
| NVMe SSDs for high-performance.
|
||||
| MinIO recommends a minimum of 8 drives per server.
|
||||
|
||||
- .. cond:: k8s
|
||||
|
||||
MinIO recommends a minimum of 4 Persistent Volumes per MinIO Server pod.
|
||||
For better performance and storage efficiency, use 8 or more PV per server.
|
||||
|
||||
.. cond:: linux or container or macos or windows
|
||||
|
||||
MinIO recommends a minimum of 4 locally attached drives per MinIO Server.
|
||||
For better performance and storage efficiency, use 8 or more drives per server.
|
||||
|
||||
Use the same type of drive (NVMe, SSD, or HDD) with the same capacity across all nodes in the deployment.
|
||||
|
||||
* - :octicon:`circle`
|
||||
@ -90,23 +103,8 @@ While MinIO can run on commodity or "budget" hardware, we strongly recommend usi
|
||||
|
||||
Prioritize securing the necessary components for each of these areas before focusing on other hardware resources, such as compute-related constraints.
|
||||
|
||||
Minimum Nodes per Deployment
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
.. cond:: k8s
|
||||
|
||||
MinIO requires a *minimum* of 4 worker nodes per MinIO Tenant with 4 drives per node.
|
||||
Each drive must consist of a Persistent Volume associated to a storage resource.
|
||||
|
||||
.. cond:: linux or container or macos or windows
|
||||
|
||||
MinIO recommends a *minimum* of 4 host servers per deployment with 4 locally attached drives per server.
|
||||
|
||||
The "4x4" topology provides a baseline of performance with tolerance for the loss of up to 4 drives *or* one node while maintaining read and write operations.
|
||||
You can increase the :ref:`erasure code parity <minio-erasure-coding>` of the deployment to improve resiliency at the cost of available storage.
|
||||
|
||||
The minimum recommendation reflects MinIO's experience with assisting enterprise customers in deploying on a variety of IT infrastructures while maintaining the desired SLA/SLO.
|
||||
While MinIO may run on less than the minimum recommended topology, any potential cost savings come at the risk of decreased reliability.
|
||||
The minimum recommendations above reflect MinIO's experience with assisting enterprise customers in deploying on a variety of IT infrastructures while maintaining the desired SLA/SLO.
|
||||
While MinIO may run on less than the minimum recommended topology, any potential cost savings come at the risk of decreased reliability, performance, or overall functionality.
|
||||
|
||||
Networking
|
||||
~~~~~~~~~~
|
||||
@ -137,11 +135,8 @@ Networking has the greatest impact on MinIO performance, where low per-host band
|
||||
The following examples of network throughput constraints assume spinning disks with ~100MB/S sustained I/O
|
||||
|
||||
- 1GbE network link can support up to 125MB/s, or one spinning disk
|
||||
- 10GbE network can support approximately 1.25GB/s, potentially supporting 10-12 spinning disk
|
||||
- 25GbE network can support approximately 3.125GB/s, potentially supporting ~30 disks
|
||||
|
||||
The recommended minimum MinIO cluster of 4 nodes with 4 drives each (16 total disks) requires a 25GbE network to support the total potential aggregate throughput.
|
||||
|
||||
- 10GbE network can support approximately 1.25GB/s, potentially supporting 10-12 spinning disks
|
||||
- 25GbE network can support approximately 3.125GB/s, potentially supporting ~30 spinning disks
|
||||
|
||||
.. _minio-hardware-checklist-memory:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user