ForkJoinPool makes task more efficient by spliting task to more subtasks , similar to map-reduce. But if the logic of the task itself cannot be split into several subtasks, what is the point of using ForkJoinPool? In reality, the logic of many actors’ receive methods cannot be split. Why can ForkJoinPool still improve efficiency?
1 post - 1 participant