Chapter 5. Minimum hardware recommendations for containerized Ceph

Ceph can run on non-proprietary commodity hardware. Small production clusters and development clusters can run without performance optimization with modest hardware.

NOTE: * Consider future growth and usage patterns when allocating disk space.

Regularly monitor disk usage and performance to address any storage limitations.
Configuring swap space for virtual memory for daemons is generally not recommended in modern systems. This approach can degrade performance, and your Ceph cluster may operate more effectively with a daemon that crashes rather than one that becomes unresponsive.

Important

Hardware accelerated compression in Ceph Object Gateway requires RHEL 9.4 on a Sapphire or Emerald Rapids Xeon CPU (or newer) with QAT devices. For more information, see Intel Ark.

Expand

Process	Criteria	Minimum Recommended
`ceph-osd-container`	Processor	1x AMD64 or Intel 64 CPU CORE per OSD container
	RAM	Minimum of 5 GB of RAM per OSD container
	OS Disk	1x OS disk per host
	OSD Storage	1x storage drive per OSD container. Cannot be shared with OS Disk.
	`block.db`	Optional, but Red Hat recommended, 1x SSD or NVMe or Optane partition or lvm per daemon. Sizing is 4% of `block.data` for BlueStore for object, file and mixed workloads and 1% of `block.data` for the BlueStore for Block Device, Openstack cinder, and Openstack cinder workloads.
	`block.wal`	Optionally, 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 `block.db` device.
	Network	2x 10 GB Ethernet NICs
`ceph-mon-container`	Processor	1x AMD64 or Intel 64 CPU CORE per mon-container
	RAM	3 GB per `mon-container`
	Disk Space Allocation	Create a dedicated Storage Partition Size for /var/lib/ceph with a minimum size of 120 GB; 240 GB is recommended. If a dedicated partition is not feasible, ensure that /var is on a dedicated partition with at least the above-mentioned free space.
	Monitor Disk	Optionally, 1x SSD disk for `Monitor rocksdb` data
	Network	2x 1GB Ethernet NICs, 10 GB Recommended
`ceph-mgr-container`	Processor	1x AMD64 or Intel 64 CPU CORE per `mgr-container`
	RAM	3 GB per `mgr-container`
	Network	2x 1GB Ethernet NICs, 10 GB Recommended
`ceph-radosgw-container`	Processor	1x AMD64 or Intel 64 CPU CORE per radosgw-container
	RAM	1 GB per daemon
	Disk Space Allocation	5 GB per daemon. The space refers to the allocation on /var/lib/ceph.
	Network	1x 1GB Ethernet NICs
`ceph-mds-container`	Processor	1x AMD64 or Intel 64 CPU CORE per mds-container
	RAM	3 GB per `mds-container` 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 `mds_cache_memory_limit` configuration setting. Note also that this is the memory for your daemon, not the overall system memory.
	Disk Space Allocation	As a best practice, create a dedicated partition for /var/log with a minimum of 20 GB of free space for this service. If a dedicated partition is not possible, ensure that /var is on a dedicated partition with at least the above-mentioned free space.
	Network	2x 1GB Ethernet NICs, 10 GB Recommended Note that this is the same network as the OSD containers. 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.

Chapter 5. Minimum hardware recommendations for containerized Ceph

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

Making open source more inclusive

About Red Hat

Theme

Red Hat legal and privacy links

Red Hat legal and privacy links