Message189798
Actors are just as vulnerable to the "new threads/processes are expensive" issue as anything else, and by using a dynamic pool appropriately you can amortise those costs across multiple instances.
The point is to expose a less opinionated threading model in a more readily accessible way. Executors and futures are *very* opinionated about the communication channels you're expected to use (the ones the executor provides), while pools are just a resource management tool. |
|
Date |
User |
Action |
Args |
2013-05-22 08:15:10 | ncoghlan | set | recipients:
+ ncoghlan, sbt, Tilka |
2013-05-22 08:15:10 | ncoghlan | set | messageid: <1369210510.63.0.708201599696.issue17140@psf.upfronthosting.co.za> |
2013-05-22 08:15:10 | ncoghlan | link | issue17140 messages |
2013-05-22 08:15:10 | ncoghlan | create | |
|