Tuning osd_memory_target and BlueStore cache
Sizing OSD memory to the host: the 4 GiB default, autotuning, minimums, how cache size affects metadata-heavy workloads and avoiding swap or OOM kills.

Tuning a running Ceph cluster: OSD memory, recovery versus client I/O, benchmarking, compression and data balance.
Sizing OSD memory to the host: the 4 GiB default, autotuning, minimums, how cache size affects metadata-heavy workloads and avoiding swap or OOM kills.
Choosing a profile when a failed drive slows applications or recovery drags on: balanced, high_client_ops and high_recovery_ops, OSD capacity benchmarks and custom settings.
Measuring what the hardware can deliver: drive and network baselines, OSD capacity benchmarks, pool-level tests that match the workload and recording results to compare after changes.
When compression saves capacity and when it costs CPU for nothing: algorithms, modes, the required ratio, blob sizes and pools that suit compression.
Fixing uneven OSD use: upmap mode, misplaced ratio limits during balancing, the deviation target and read balancing for primary PGs on Reef and later clients.

Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.