Chapter 5. Minimum hardware recommendations
Ceph can run on non-proprietary commodity hardware. Small production clusters and development clusters can run without performance optimization with modest hardware.
Disk space requirements are based on the Ceph daemons' default path under /var/lib/ceph/
directory.
Process | Criteria | Minimum Recommended |
---|---|---|
| Processor | 1x AMD64 or Intel 64 |
RAM |
For | |
OS Disk | 1x OS disk per host | |
Volume Storage | 1x storage drive per daemon | |
|
Optional, but Red Hat recommended, 1x SSD or NVMe or Optane partition or logical volume per daemon. Sizing is 4% of | |
|
Optional, 1x SSD or NVMe or Optane partition or logical volume per daemon. Use a small size, for example 10 GB, and only if it’s faster than the | |
Network | 2x 1GB Ethernet NICs | |
| Processor | 1x AMD64 or Intel 64 |
RAM | 1 GB per daemon | |
Disk Space | 15 GB per daemon (50 GB recommended) | |
Monitor Disk |
Optionally,1x SSD disk for | |
Network | 2x 1 GB Ethernet NICs | |
| Processor | 1x AMD64 or Intel 64 |
RAM | 1 GB per daemon | |
Network | 2x 1 GB Ethernet NICs | |
| Processor | 1x AMD64 or Intel 64 |
RAM | 1 GB per daemon | |
Disk Space | 5 GB per daemon | |
Network | 1x 1 GB Ethernet NICs | |
| Processor | 1x AMD64 or Intel 64 |
RAM | 2 GB per daemon
This number is highly dependent on the configurable MDS cache size. The RAM requirement is typically twice as much as the amount set in the | |
Disk Space | 2 MB per daemon, plus any space required for logging, which might vary depending on the configured log levels. | |
Network | 2x 1 GB Ethernet NICs Note that this is the same network as the OSDs. If you have a 10 GB network on your OSDs you should use the same on your MDS so that the MDS is not disadvantaged when it comes to latency. |