From c446d743a2dbde91512da725d8e3b301413b01dc Mon Sep 17 00:00:00 2001 From: Kleis Auke Wolthuizen Date: Sat, 20 Sep 2025 14:03:38 +0200 Subject: [PATCH] Docs: libvips manages its own thread pool (#4455) --- docs/src/content/docs/performance.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/src/content/docs/performance.md b/docs/src/content/docs/performance.md index b244dbe5..19aead63 100644 --- a/docs/src/content/docs/performance.md +++ b/docs/src/content/docs/performance.md @@ -17,8 +17,8 @@ before the Node.js process starts to increase the thread pool size. export UV_THREADPOOL_SIZE="$(lscpu -p | egrep -v "^#" | sort -u -t, -k 2,4 | wc -l)" ``` -libvips uses a glib-managed thread pool to avoid the overhead of spawning new threads. -The size of the shared thread pool will grow on demand and shrink when idle. +libvips uses a shared thread pool to avoid the overhead of spawning new threads. +The size of this thread pool will grow on demand and shrink when idle. The default number of threads used to concurrently process each image is the same as the number of CPU cores, except when using glibc-based Linux without jemalloc, where the default is `1` to help reduce memory fragmentation.