Mathis/sharp
1
0
Fork 0
mirror of https://github.com/lovell/sharp.git synced 2025-12-06 03:51:40 +01:00
Code Issues Packages Projects Releases Wiki Activity

Docs: libvips manages its own thread pool (#4455)

Browse Source
This commit is contained in:
Kleis Auke Wolthuizen 2025-09-20 14:03:38 +02:00 committed by GitHub
parent 3498eb63e3
commit c446d743a2
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/src/content/docs/performance.md
View File

@ -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)" 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. libvips uses a shared 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. 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, 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. except when using glibc-based Linux without jemalloc, where the default is `1` to help reduce memory fragmentation.