From b3a4e4ead205426bd44977c4e19069c35458bad5 Mon Sep 17 00:00:00 2001 From: alexey-milovidov Date: Thu, 24 Feb 2022 20:47:15 +0300 Subject: [PATCH] Update website/blog/en/2022/clickhouse-v22.2-released.md Co-authored-by: Christoph Wurm --- website/blog/en/2022/clickhouse-v22.2-released.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/blog/en/2022/clickhouse-v22.2-released.md b/website/blog/en/2022/clickhouse-v22.2-released.md index 73d6637e41a..528654135f5 100644 --- a/website/blog/en/2022/clickhouse-v22.2-released.md +++ b/website/blog/en/2022/clickhouse-v22.2-released.md @@ -72,7 +72,7 @@ We split per-query and per-user memory limits into a pair of hard and soft limit A query will be allowed to use more memory than a soft limit if there is available memory. But if there will be memory shortage (relative to the per-user hard limit or total per-server memory consumption), we calculate the "overcommit ratio" - how much more memory every query is consuming relative to the soft limit - and we will kill the most overcommitted query to let other queries run. -In short, your query will not be limited to a few gigabytes of RAM if you have hundreds gigabytes available. +In short, your query will not be limited to a few gigabytes of RAM if you have hundreds of gigabytes available. This experimental feature is implemented by **Dmitry Novik** and is continuing to be developed.