-
Notifications
You must be signed in to change notification settings - Fork 24
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
dask tutorial #20
Comments
With the changes in MDAnalysis/pmda#66 and the new way to globally define the scheduler it becomes even more useful to have a solid introduction to dask. @dotsdl please can you make sure that the new idiom to set the scheduler, which @kain88-de explained in MDAnalysis/pmda#66 (comment), is also covered? |
With PMDA now using dask's preferred way to select a scheduler, EDIT: As @kain88-de says below we still use multiprocessing as default. It will still be useful to show how to set up distributed and talk about the schedulers, though. Also worthwhile pointing out that the threaded scheduler will not work well with PMDA. |
If people don’t change the scheduler setting we pick multiprocessing. We
should add to the pmda docs that thread scheduler doesn’t work with pmda.
…On Thu 1. Nov 2018 at 23:51, Oliver Beckstein ***@***.***> wrote:
With PMDA now using dask's preferred way to select a scheduler, we now
have to teach people to explicitly set the *multiprocessing* or
*distributed* scheduler and *not* the default *threaded* scheduler.
Threaded does not work well with our largely Python based code.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#20 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AEGnVlxf_NXdiKjnAX9KYZN5GhX4Me9rks5uq3sEgaJpZM4Xz1L2>
.
|
Yes, you're right. (I didn't think of adding ad note regarding the threaded scheduler in MDAnalysis/pmda#78.) |
introductory tutorial on dask
The text was updated successfully, but these errors were encountered: