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

pmap(f, c; distributed=false is not equivalent to asyncmap(f, c) #19652

Closed
rofinn opened this issue Dec 19, 2016 · 2 comments
Closed

pmap(f, c; distributed=false is not equivalent to asyncmap(f, c) #19652

rofinn opened this issue Dec 19, 2016 · 2 comments
Assignees
Labels
docs This change adds or pertains to documentation parallelism Parallel or distributed computation

Comments

@rofinn
Copy link
Contributor

rofinn commented Dec 19, 2016

In the docs the following calls are described as equivalent.

pmap(f,c; distributed=false) and asyncmap(f,c)

However, the pmap call will only run an asyncmap with ntasks equal to nworkers(p) (as shown here) while the asyncmap call will run a Task for each element of c. If this is the intended behaviour it would help to mention it in the docs to avoid confusion.

@kshyatt kshyatt added docs This change adds or pertains to documentation parallelism Parallel or distributed computation labels Dec 19, 2016
@amitmurthy amitmurthy self-assigned this Dec 20, 2016
@amitmurthy
Copy link
Contributor

Just adding a reminder to also handle ExponentialBackOff in the pmap retry case when closing this issue (#19331 (comment))

@rofinn
Copy link
Contributor Author

rofinn commented Jan 17, 2017

Thanks @amitmurthy!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs This change adds or pertains to documentation parallelism Parallel or distributed computation
Projects
None yet
Development

No branches or pull requests

3 participants