JuliaLang / JuliaLang/Distributed.jl
Nested PMAP calls do not work
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 55
- Forks
- 19
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
the following code with has nested pmap functions, it hangs even if I execute it with 1 single process addprocs(1).
using Distributed
@everywhere function inner_process(task_id)
task_id^2
end
@everywhere function outer_process(job_id)
inner_task = collect(1:2)
pmap(inner_process, inner_task)
end
function do_job(jobs_list)
pmap(outer_process, jobs_list)
end
jobs_list = collect(1:10)
do_job(jobs_list)
This is the version I am using
julia> versioninfo()
Julia Version 1.1.0
Commit 80516ca202 (2019-01-21 21:24 UTC)
Platform Info:
OS: Windows (x86_64-w64-mingw32)
CPU: Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz
WORD_SIZE: 64
LIBM: libopenlibm
LLVM: libLLVM-6.0.1 (ORCJIT, skylake)
Environment:
export JULIA_NUM_THREADS = 4
JULIA_DEPOT_PATH = C:\Program Files\ReSolver.DistributedJulia\depot
JULIA_EDITOR = C:\Users\AppData\Local\atom\atom.exe
JULIA_NUM_THREADS = 4
JULIA_PKGDIR = C:\Program Files\ReSolver.DistributedJulia\packages
Am I maybe misunderstanding the feature or is this an expected behavior?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running the nested pmap example from the issue with Julia 1.1.0 and one worker, then inspect the pmap entry point and its worker scheduling behavior. Determine whether nested calls are supported and identify the expected behavior for this example; a fix or clear documentation of the limitation would define completion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100