foreach (or virtually anything you might use for concurrent programming)
only really makes sense if the work the clients are doing is substantial
enough to overwhelm the communication overhead. And there are many ways to
accomplish the same task more or less efficiently (for example, doing blocks
Hi,
I think I lost the reference email somewhere, but:
Not only is the sequential foreach much slower than the simple
for-loop (as least in this particular instance), but I am not quite
sure how to make foreach run parallel. Where would I get this parallel
backend? I looked at doMC and
John, Steve, thank you for answering my post!
On Wed, Jun 16, 2010 at 20:55, Steve Lianoglou
mailinglist.honey...@gmail.com wrote:
Hi,
I think I lost the reference email somewhere, but:
Not only is the sequential foreach much slower than the simple
for-loop (as least in this particular
Hi all,
Just for the record, this is the link to the blog post:
http://www.r-statistics.com/2010/04/parallel-multicore-processing-with-r-on-windows/
You can run work in parallel in multiple processors. Although it is only
worthwhile when each task takes a long time to run (I give an example to
4 matches
Mail list logo
