NodeJS is well known for being single-threading, but it is not true, because only the event-loop is handled by a single thread. NodeJS gives to us ...
Some comments have been hidden by the post's author - find out more
For further actions, you may consider blocking this person and/or reporting abuse
You don't need multiple threads to upload multiple files in parallel in Node - the single threaded part is only on the instruction pipeline, you could easilly issue 100 uploads and have them run in parallel using a
Promise.all()- the Async library has lots of useful calls to batch up things too if you don't just want to start all at once.Multiple threads and processes are very handy if you are actually doing processing in your Javascript code, where other operations would be blocked.
Makes sense! thanks for your comment!
Hello ! Don't hesitate to put colors on your
codeblocklike this example for have to have a better understanding of your code 😎Thanks a lot! I didnt know that
You don't need multithreading to upload files concurrently in NodeJS.
NodeJS is not C++ where I/O operations are synchronous by default.
All I/O operations are always async in NodeJS. There are some exceptions though, like synchronous I/O APIs but they are very bad for performance so don't use them.
NodeJS uses libuv to issue non-blocking I/O syscalls and to get I/O event notifications.
Create Workers in NodeJS, only if you are doing CPU bound operations like computing hash of a large ArrayBuffer, or a very simple example would be finding a prime number. These operations will put heavy load on the CPU thread and prevent other tasks from executing.
It is always better to do I/O based operations in an async event loop as OS threads/processes are very expensive. When doing I/O, most of the time, our application spends waiting for a Disk or a Network Device.
If you know Rust see Tokio and Rayon.
See here to learn how Nginx delivers high performance with Non Blocking I/O.
Makes sense! thanks for your comment!
This approach I used to show how to create worker threads, perhaps is not the best!
Awesome insights!
Thanks a lot for sharing such concepts on a perfectly reasonable use-case, 10 out of 10 😁
Thanks a lot for your comment!
I am planning to write more contents to show the things under the hood.
That would be amazing! I'm following you to read more about these topics as soon as you publish them 😄
Nice article, about that conceptual part in the introduction, wouldn't
child_processbe an approach for multiprocessing instead of multithreading?Good point! Parallel processing should be the best word for that!
thanks for your comment!
i like the 'piscina' library for using multiple thread in node.js, however shared memory would still be awesome.
Nice! I know it. It was created by a brazilian guy I guess.