From 42c212cf96f530e6b7edf1626ea1f73b16774f1f Mon Sep 17 00:00:00 2001 From: David Myriel Date: Wed, 6 Mar 2024 08:51:59 +0100 Subject: [PATCH] Update qdrant-landing/content/blog/qdrant-1.8.x.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Tim Visée --- qdrant-landing/content/blog/qdrant-1.8.x.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/qdrant-landing/content/blog/qdrant-1.8.x.md b/qdrant-landing/content/blog/qdrant-1.8.x.md index ae0993b87..b72bea7f8 100644 --- a/qdrant-landing/content/blog/qdrant-1.8.x.md +++ b/qdrant-landing/content/blog/qdrant-1.8.x.md @@ -66,9 +66,8 @@ This version introduces a `optimizer_cpu_budget` parameter to control the maximu > Read more about `config.yaml` in the [Configuration document](https://qdrant.tech/documentation/guides/configuration/). ```yaml + # CPU budget, how many CPUs (threads) to allocate for an optimization job. optimizer_cpu_budget: 0 - # CPU budget, how many CPUs (threads) to allocate for an optimization job. -``` - If left at 0, Qdrant will keep 1 or more CPUs unallocated - depending on CPU size. - If the setting is positive, Qdrant will use this exact number of CPUs for indexing. - If the setting is negative, Qdrant will subtract this number of CPUs from the available CPUs for indexing.