3 ms·
Actor's are fantastic and ideal for many situations. However, this thread pool is specifically for _high performance_ computing which generally means working w
by elcritch 4y ago
Actor's are fantastic and ideal for many situations.
However, this thread pool is specifically for _high performance_ computing which generally means working with shared memory. The actor paradigm generally assumes no shared memory and communications using message passing. It's harder to optimize performance and is an impedance mismatch for HPC.
- _0w8t 4y agoAnother important difference from the actor model is that the library uses a future interface with blocking wait to get the results. With actors there is no wait as the results are posted to the message queue of the caller. But waiting makes the usage more similar to sequential computing code. When there is an opportunity the code starts several jobs to work on presumably independent data sets, then waits for their results in a shared memory and then process them sequentially until there is another opportunity for parallel computation.