Skip to content
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 (Multi) Threads #1473

Closed
druny opened this issue Sep 2, 2018 · 4 comments
Closed

Worker (Multi) Threads #1473

druny opened this issue Sep 2, 2018 · 4 comments

Comments

@druny
Copy link

druny commented Sep 2, 2018

https://nodejs.org/api/worker_threads.html
Hello Guys. I am started working with lecture for JS conf with theme about multi threading in NodeJs. I will so much appreciate, if it possible, get answers on my questions:

  1. What Your team think about this.
  2. What current status of the module.
  3. When We be able expect stable version.
  4. What hardest things meet, in implementation process
  5. What do You think about it? Do it good idea?
  6. What about future plans
    It will be fine if NodeJS team answer at least on one quastion
    With best wishes. Thank you in advance
@addaleax
Copy link
Member

addaleax commented Sep 2, 2018

Hi! This is a perfectly timed question, given that I’m just finishing up my notes for my talk about it at http://nordicjs.com/ this week! 😄

When We be able expect stable version.

To a large degree, that depends on how much and what kind of feedback we get from our users. There’s no fixed time frame here.

What hardest things meet, in implementation process

Windows support, during some of the work leading up to it. nodejs/node#19377 was blocked on that for 2 months, with no progress being made.

What current status of the module.

It’s experimental, meaning that we consider us free to make changes to it at any time, including breaking changes if necessary. However, I do think that we are committed to keeping this feature and the general API idea around.

What about future plans

We’re looking for feedback, but generally, there are no large shifts in the feature currently planned.

Some things that I’d like to see and that I’ll try to make happen:

  • Passing native handles around (e.g. sockets)
  • (Some form of) Deadlock detection
  • Naming individual threads

I’m not going to answer the “what do you think about it” questions, I think I’m a tad too biased for that. 😉

@AyushG3112
Copy link

I personally believe worker_threads are a great way to perform synchronous processing in nodejs without blocking the event loop of the main thread by delegating the processing to a worker(considering workers have their own event loop)

@gireeshpunathil
Copy link
Member

@druny - are there outstanding questions that need answer? or else are we good to close this?

@druny
Copy link
Author

druny commented Jun 10, 2019

@gireeshpunathil It's ok for me. Thank You

@druny druny closed this as completed Jun 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants