JuliaParallel / JuliaParallel/DistributedArrays.jl
Expand documentation
- Lenguaje dominante
- Julia
- Estrellas
- 205
- Forks
- 34
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
We are finding the documentation for DistributedArrays to be lacking in a few ways:
1. There is no description of the actual DistributedArray type. It would be helpful to know how DistributedArrays are stored across processes. A lot of people who are using DistributedArrays are experienced at distributed programming, and will find it helpful to know how things are implemented. For instance, it would be helpful to get an idea (without looking at the source code) of how the local parts are tied together in a single type.
2. When are values copied/not copied? For example:
```julia
da = dzeros(100,100)
sa = da[1:10, 35:50]
out = convert(DArray, sa)
```
Does the last line here copy the values of `sa`? More generally, information about performance would be really useful, as well as some performance tips.
3. Expound a bit more on DArray constructor. Perhaps an example somewhere between `dfill` and the Game of Life would help, like this:
```julia
procs = addprocs(5)
# Construct a DArray
da = DArray((2,5), procs, [1,5]) do I
# construct a local part
localpart = Array{Float64}(2,1)
for i in first(I) # first(I) = 1:2
localpart[i] = i
end
return localpart
end
```
It would help to describe this example as follows:
This DArray is distributed so that each of 5 processes holds one column. `I` is a tuple of indices describing the indices of the DArray that reside on a given process. On the first process, `I = (1:2,1:1)`. In the `init` function, we construct the local column as a regular `Array` and return it to the `DArray` constructor. Note that it is important to return `localpart`: if we don't do this, then Julia returns the last variable that was assigned, which is `localpart[2]` - but the `DArray` constructor is expecting an array.
cc @pearlzli
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Evaluación
Este issue todavía no se ha evaluado.