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
[feat] worker thread pool and other performance optimizations #45
Labels
enhancement
New feature or request
Comments
This would be absolutely sick to have. I know that definitely some processes run WAY faster when not in worker threads - but the whole idea is the job isolation in their own threads (which is the "better" approach). I guess just get a faster CPU 😄 |
naz
changed the title
[feat] worker thread pool and other pefromance optimizations
[feat] worker thread pool and other performance optimizations
Nov 18, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Was looking into how resource intensive worker creation is through bree. I did not come across concrete numbers of the overhead associated with worker_thread instantiation. Based on the reference below it should not be considered as a "cheap" operation to run.
From Node.js worker threads documentation:
(linked Worker thread pool implementation)
Was wondering if there are concrete performance metrics available illustrating an overhead associated with worker thread creation? Is it planned to utilize worker thread pool pattern (there's a Pool implementation available in bthreads)
Another idea I was contemplating was around optimizing non-CPU intensive jobs. Would it make sense to bypass worker creation and run such jobs in the main thread without breaking out of event loop? What's the threshold which would determine if it's more resource efficient to run the task on the main thread or offload it to a worker thread?
The text was updated successfully, but these errors were encountered: