Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Piscina – The Node.js Worker Pool

github.com

Post reply on HN
Print view View original

1–10 of 51 posts

Re: Piscina – The Node.js Worker Pool

#5

Post by curben »

freeqaz wrote: post #2

Does anybody use this or anything similar? If so, what problems are you solving?

AFAIK this is a wrapper of worker_threads API. https://github.com/tuananh/camaro utilises this for multi-threading processing of XML input. Hexo (static site generator) is attempting to utilise this library (https://github.com/hexojs/hexo/issues/4355).

Re: Piscina – The Node.js Worker Pool

#7

Post by Etheryte »

freeqaz wrote: post #2

Does anybody use this or anything similar? If so, what problems are you solving?

The worker API in Javascript is quite a pain to use, but needless to say multithreading is invaluable in many contexts, both in the browser and in Node. I haven't used this library but it seems to solve a similar problem to other ones in the same space — make writing multithreaded code sane, allowing you to avoid writing a bunch of repetitive boilerplate.

Re: Piscina – The Node.js Worker Pool

#9

Post by ddoolin »

freeqaz wrote: post #2

Does anybody use this or anything similar? If so, what problems are you solving?

We use worker threads directly to process large unorganized (for the browser) datasets and do some deductions before it hits the store.

We also have a worker thread blocked on a redis channel that acts as a queue.

Post reply on HN