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 pool suggestion #13

Closed
maxogden opened this issue Nov 10, 2013 · 1 comment
Closed

worker pool suggestion #13

maxogden opened this issue Nov 10, 2013 · 1 comment

Comments

@maxogden
Copy link

@maxogden maxogden commented Nov 10, 2013

https://github.com/shama/workerify is a nice way to write modular code that uses web workers

@feross

This comment has been minimized.

Copy link
Member

@feross feross commented Nov 11, 2013

Neat - workerify looks handy.

For PeerCDN, I inlined workers the same way that workerify does. This was before I knew about browserify.

I'm just wondering what the right overall webworker approach is now -- pool vs. creating a new worker every time there's a cpu-intensive task to perform. Do you know what the startup time for a worker is like? I'll probably have to test this.

@feross feross closed this Jul 25, 2014
@lock lock bot locked as resolved and limited conversation to collaborators May 7, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.