I found this module while looking for a fast image compositing library, and my immediate question was "how does this interact with NodeJS's event loop and what will the performance impact on my app be if I use it in a web application on a multi core machine".
I decided to dig around the source code and find out for myself, this is the result of my enquiries.
Coverage remained the same at 98.311% when pulling b5d5770ec81c27396e7b9cd1c5b9f5932f5331b5 on BernieSumption:patch-1 into a65f6086a26c22736eb4d7cfa43c096afad5b5e8 on EyalAr:master.
I found this module while looking for a fast image compositing library, and my immediate question was "how does this interact with NodeJS's event loop and what will the performance impact on my app be if I use it in a web application on a multi core machine".
I decided to dig around the source code and find out for myself, this is the result of my enquiries.
For the record, the path was: lwip's *Worker classes > NAN's AsyncQueueWorker > uv_queue_work > this page on threading performance