What would you say typically limits taskPR's approach, not finding
enough instruction-level parallelism at the R script level, or the
communications overhead (probably latency) of trying to make use of
it?
Depends on the specific function. The communication cost is
significant, especially seri
On Thu, Sep 04, 2008 at 04:06:31PM -0400, David Bauer wrote:
> taskPR was an attempt to get 'free' parallelism out of already
> existing programs by using simple data dependencies to figure out
> which individual statements in a program can be run in parallel.
> The name comes from the description
> - taskPR: Sounds equivalent to snow. Also uses MPI underneath.
Actually, it is very different from snow. taskPR was an attempt to get 'free'
parallelism out of already existing programs by using simple data dependencies
to figure out which individual statements in a program can be run in pa
I see about 7 different R packages for multi-process parallel
programming. Which do you think is the best, most complete, and most
robust to pick for general purpose Erlang-style message-passing
programming in R, and why?
First here's my use case, and then my analysis so far. I often have
code w
