On problems with threads in Node.js
future-processing.pl
On problems with threads in Node.js
1–10 of 66 posts
Re: On problems with threads in Node.js
#2Piece of badly engineered software conquering the world. As if more JavaScript was really something worth pursuing.
Re: On problems with threads in Node.js
#3Piece of badly engineered software conquering the world. As if more JavaScript was really something worth pursuing.
Can't upvote enough!
Re: On problems with threads in Node.js
#4Piece of badly engineered software conquering the world. As if more JavaScript was really something worth pursuing.
comments like that are making me reading even fewer comments on HN...
Re: On problems with threads in Node.js
#5To sum it up: node.js runs only 4 background threads. Be aware of this.
No big deal really. I have multiple servers running node.js under load for 3+ years and never had an issue with this.
In fact, I found it helpful. If your database is under load and is already running 4 heavy queries, not giving it any more jobs is actually a good thing.
Re: On problems with threads in Node.js
#6To sum it up: node.js runs only 4 background threads. Be aware of this. No big deal really. I have multiple servers running node.js under load for 3+ years and never had an issue with this. In fact, I found it helpful. If your database is under load and is already running 4 heavy queries, not giving it any more jobs is actually a good thing.
On the other hand, not being able to hit the filesystem because you have those four queries running is... not so helpful.
In general, this looks like it could be a performance bottleneck for highly-concurrent applications.
Re: On problems with threads in Node.js
#7To sum it up: node.js runs only 4 background threads. Be aware of this. No big deal really. I have multiple servers running node.js under load for 3+ years and never had an issue with this. In fact, I found it helpful. If your database is under load and is already running 4 heavy queries, not giving it any more jobs is actually a good thing.
On the other hand, not being able to hit the filesystem because you have those four queries running is... not so helpful. In general, this looks like it could be a performance bottleneck for highly-concurrent applications.
[deleted]
Re: On problems with threads in Node.js
#8Thank you for sharing your findings here. Very pertinent to me right now - could actually drastically minimise the amount of research I have to do today. I love HN.
Re: On problems with threads in Node.js
#9It's worth noting that DB drivers that actually integrate with libuv are a minority - most DB divers use Node-level network APIs and are unaffected by such thread pool limits.
Re: On problems with threads in Node.js
#10Is this another case of "here's the code I ran" when in fact they didn't? There should be 3 lines of output, not 6!
Also, the code says it will print the time taken since the start of the program, which again doesn't go with the output and the conclusion being made!
Anyway, how come the output isn't in order?