[pve-devel] applied: [PATCH docs] pveceph: reword memory precondition

Thomas Lamprecht t.lamprecht at proxmox.com
Wed Feb 19 16:51:50 CET 2020


On 2/17/20 3:02 PM, Alwin Antreich wrote:
> and add the memory target for OSDs, included since Luminous. As well as
> distinguish the memory usage between the OSD backends.
> 
> Signed-off-by: Alwin Antreich <a.antreich at proxmox.com>
> ---
>  pveceph.adoc | 13 ++++++++++---
>  1 file changed, 10 insertions(+), 3 deletions(-)
> 
> diff --git a/pveceph.adoc b/pveceph.adoc
> index b3bbadf..8dc8568 100644
> --- a/pveceph.adoc
> +++ b/pveceph.adoc
> @@ -86,9 +86,16 @@ provide enough resources for stable and durable Ceph performance.
>  .Memory
>  Especially in a hyper-converged setup, the memory consumption needs to be
>  carefully monitored. In addition to the intended workload from virtual machines
> -and container, Ceph needs enough memory available to provide good and stable
> -performance. As a rule of thumb, for roughly 1 TiB of data, 1 GiB of memory
> -will be used by an OSD. OSD caching will use additional memory.
> +and containers, Ceph needs enough memory available to provide excellent and
> +stable performance.
> +
> +As a rule of thumb, for roughly **1 TiB of data, 1 GiB of memory** will be used
> +by an OSD. Especially during recovery, rebalancing or backfilling.
> +
> +The daemon itself will use additional memory. The Bluestore backend of the
> +daemon requires by default **3-5 GiB of memory** (adjustable). In contrast, the
> +legacy Filestore backend uses the OS page cache and the memory consumption is
> +generally related to PGs of an OSD daemon.
>  
>  .Network
>  We recommend a network bandwidth of at least 10 GbE or more, which is used
> 

applied, thanks!




More information about the pve-devel mailing list