std.parallelism equivalents for posix fork and multi-machine processing

[Laeeth Isharc via Digitalmars-d]

On Thursday, 14 May 2015 at 20:15:38 UTC, Ola Fosheim Grøstad 
wrote:
> On Thursday, 14 May 2015 at 20:06:55 UTC, Laeeth Isharc wrote:
>> To start the process off (because small beginnings are better 
>> than no beginning): what are the key features of processes vs 
>> threads one would need to bear in mind when designing such a 
>> thing?  Because I spent the past couple of decades in a 
>> different field, multiprocessing passed me by, so I am only 
>> now slowly catching up.
>
> "nobody" understands multiprocessing. Or rather… you need to 
> understand the hardware and the concrete problem space first. 
> There are no general solutions.

Yes, I certainly understand that it is a highly specialist and 
complex area where the best minds in the world have not yet the 
answers.  So if one were addressing the problem from a computer 
science academic perspective, then perhaps one will arrive at a 
different answer.

My own is a pragmatic commercial one.  I have some problems which 
perhaps scale quite well, and rather than write it using fork 
directly, I would rather have a higher level wrapper along the 
lines of std.parallelism.  Perhaps such would be flawed and 
limited, but often something is better than nothing, even if not 
perfect.  And I mention it on the forum only because usually I 
have found the problems I face turn out to be those faced by many 
others too..

If you have any thoughts on what should be considered, I would 
very much appreciate them.  (And I owe you a response on our last 
suspended discussion, but haven't had time of late).


Laeeth.