-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Worker Threads: segmentation fault #1297
Comments
https://nodejs.org/api/worker_threads.html#worker_threads_class_worker says:
Worker threads are designed for CPU-intensive JavaScript so would be unlikely to help sharp/libvips, which is compiled C/C++, makes effective use of CPUs and is typically I/O bound. http://sharp.pixelplumbing.com/en/stable/api-utility/#concurrency provides details of the concurrency and parallelism options available. |
So, sharp dont block event loop? |
That's correct, all image processing already occurs on threads from the the libuv pool (plus threads spawned by libvips) - see http://sharp.pixelplumbing.com/en/stable/#fast
|
Hello.
My Code
I run this code in Worker Threads.
Arch linux, node 10.5.0, latest sharp
The text was updated successfully, but these errors were encountered: