From ccb851d2a431647124754e1252df66ed11d0e900 Mon Sep 17 00:00:00 2001 From: Zac Dover Date: Sun, 3 Mar 2024 20:28:00 +1000 Subject: [PATCH] doc/rados: remove PGcalc from docs Remove mention of the "PG calc" tool from the documentation. I have removed all mention of this in one fell swoop to help posterity restore mention of this tool if we decide we need to do so. Signed-off-by: Zac Dover --- doc/rados/operations/placement-groups.rst | 4 ---- doc/rados/operations/pools.rst | 19 ++++++++----------- doc/radosgw/pools.rst | 17 +++++++---------- 3 files changed, 15 insertions(+), 25 deletions(-) diff --git a/doc/rados/operations/placement-groups.rst b/doc/rados/operations/placement-groups.rst index f9b87528b5288..84dad884e22bc 100644 --- a/doc/rados/operations/placement-groups.rst +++ b/doc/rados/operations/placement-groups.rst @@ -641,9 +641,6 @@ pools, each with 512 PGs on 10 OSDs, the OSDs will have to handle ~50,000 PGs each. This cluster will require significantly more resources and significantly more time for peering. -For determining the optimal number of PGs per OSD, we recommend the `PGCalc`_ -tool. - .. _setting the number of placement groups: @@ -935,4 +932,3 @@ about it entirely (if it is too new to have a previous version). To mark the .. _Create a Pool: ../pools#createpool .. _Mapping PGs to OSDs: ../../../architecture#mapping-pgs-to-osds -.. _pgcalc: https://old.ceph.com/pgcalc/ diff --git a/doc/rados/operations/pools.rst b/doc/rados/operations/pools.rst index afe9926589a4a..e1770c8087a40 100644 --- a/doc/rados/operations/pools.rst +++ b/doc/rados/operations/pools.rst @@ -18,15 +18,14 @@ Pools provide: <../erasure-code>`_, resilience is defined as the number of coding chunks (for example, ``m = 2`` in the default **erasure code profile**). -- **Placement Groups**: You can set the number of placement groups (PGs) for - the pool. In a typical configuration, the target number of PGs is - approximately one hundred PGs per OSD. This provides reasonable balancing - without consuming excessive computing resources. When setting up multiple - pools, be careful to set an appropriate number of PGs for each pool and for - the cluster as a whole. Each PG belongs to a specific pool: when multiple - pools use the same OSDs, make sure that the **sum** of PG replicas per OSD is - in the desired PG-per-OSD target range. To calculate an appropriate number of - PGs for your pools, use the `pgcalc`_ tool. +- **Placement Groups**: The :ref:`autoscaler ` sets the number + of placement groups (PGs) for the pool. In a typical configuration, the + target number of PGs is approximately one-hundred and fifty PGs per OSD. This + provides reasonable balancing without consuming excessive computing + resources. When setting up multiple pools, set an appropriate number of PGs + for each pool and for the cluster as a whole. Each PG belongs to a specific + pool: when multiple pools use the same OSDs, make sure that the **sum** of PG + replicas per OSD is in the desired PG-per-OSD target range. - **CRUSH Rules**: When data is stored in a pool, the placement of the object and its replicas (or chunks, in the case of erasure-coded pools) in your @@ -735,8 +734,6 @@ Managing pools that are flagged with ``--bulk`` =============================================== See :ref:`managing_bulk_flagged_pools`. - -.. _pgcalc: https://old.ceph.com/pgcalc/ .. _Pool, PG and CRUSH Config Reference: ../../configuration/pool-pg-config-ref .. _Bloom Filter: https://en.wikipedia.org/wiki/Bloom_filter .. _setting the number of placement groups: ../placement-groups#set-the-number-of-placement-groups diff --git a/doc/radosgw/pools.rst b/doc/radosgw/pools.rst index bb1246c1fcac9..acd6a63211459 100644 --- a/doc/radosgw/pools.rst +++ b/doc/radosgw/pools.rst @@ -11,16 +11,13 @@ multiple zones. Tuning ====== -When ``radosgw`` first tries to operate on a zone pool that does not -exist, it will create that pool with the default values from -``osd pool default pg num`` and ``osd pool default pgp num``. These defaults -are sufficient for some pools, but others (especially those listed in -``placement_pools`` for the bucket index and data) will require additional -tuning. We recommend using the `Ceph Placement Group’s per Pool -Calculator `__ to calculate a suitable number of -placement groups for these pools. See -`Pools `__ -for details on pool creation. +When ``radosgw`` first tries to operate on a zone pool that does not exist, it +will create that pool with the default values from ``osd pool default pg num`` +and ``osd pool default pgp num``. These defaults are sufficient for some pools, +but others (especially those listed in ``placement_pools`` for the bucket index +and data) will require additional tuning. See `Pools +`__ for details +on pool creation. .. _radosgw-pool-namespaces: -- 2.39.5