From fc2aa896de278d0f7df5fd41f384347882119708 Mon Sep 17 00:00:00 2001 From: Denny Crane Date: Fri, 27 Dec 2024 14:26:27 -0400 Subject: [PATCH] Update altinity-kb-number-of-active-parts-in-a-partition.md --- .../altinity-kb-number-of-active-parts-in-a-partition.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/altinity-kb-useful-queries/altinity-kb-number-of-active-parts-in-a-partition.md b/content/en/altinity-kb-useful-queries/altinity-kb-number-of-active-parts-in-a-partition.md index f8107d0909..44e6f043eb 100644 --- a/content/en/altinity-kb-useful-queries/altinity-kb-number-of-active-parts-in-a-partition.md +++ b/content/en/altinity-kb-useful-queries/altinity-kb-number-of-active-parts-in-a-partition.md @@ -14,7 +14,7 @@ CH merge scheduler balances between a big number of parts and a wasting resource Merges are CPU/DISK IO expensive. If CH will merge every new part then all resources will be spend on merges and will no resources remain on queries (selects ). -CH will not merge parts with a combined size greater than 100 GB. +CH will not merge parts with a combined size greater than 150 GB [max_bytes_to_merge_at_max_space_in_pool](https://clickhouse.com/docs/en/operations/settings/merge-tree-settings#max-bytes-to-merge-at-max-space-in-pool). ``` SELECT