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

Implement parallel Map & Reduce #40

Open
aysyal31 opened this issue Jul 30, 2018 · 3 comments
Open

Implement parallel Map & Reduce #40

aysyal31 opened this issue Jul 30, 2018 · 3 comments

Comments

@aysyal31
Copy link

Hi Team ,

We are using workerpool for executing certain functions for an array of items.

As of current implementation, the full array is passed onto all the workers for processing.
Ideally we would want a map & reduce functionality where the array is distributed among the workers in chunks and the workers upon completion return the worked upon array.

Any direction on helping achieve that would be great. We can open for any contributions to the code if reqd.

@josdejong
Copy link
Owner

Parallel execution of operations on arrays would be great. This is even one of the bullets in the roadmap:

https://github.com/josdejong/workerpool#roadmap

Help implementing this would be very welcome!

I haven't thought about how something like this can be implemented efficiently. Do you have any ideas already?

I guess we have to create a sort of an "ArrayTask" where workers can pick a single item+task from (without removing the task itself from the queue), report the results back, and only when all items are processed, run the callback of the ArrayTask with the results and remove the ArrayTask from the queue.

@joeyrobert
Copy link

I wrote this snippet recently leveraging worker pool, maybe it could be of use:

function mapParallel(func, items) {
    var pool = workerpool.pool();
    var promises = items.map(item => pool.exec(func, [item]));
    return Promise.all(promises);
}

@josdejong
Copy link
Owner

Thanks for sharing Joey. I see inside the function you create a new pool. You probably want to destroy it after all promises are done to free up resources, or instead you could create a singleton instance of a workerpool.

maybephilipp pushed a commit to maybephilipp/workerpool that referenced this issue Sep 27, 2020
* waiting clear local storage

* Implementing skipping aut if navigate to jobs

* WIP

Co-authored-by: Aleksey Gerasimov <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants