3 ms·
The way this problems change in Scala is not by using the parallel collections library, but by using Akka straight up, or using Spark. Akka is an actor system
by hibikir 12y ago
The way this problems change in Scala is not by using the parallel collections library, but by using Akka straight up, or using Spark.
Akka is an actor system framework, so it's extremely well suited for this problem.
Spark can process tremendous amounts of data in parallel, even over hundreds of machines if you really have the iron, and works just as well with just one machine.
You can technically use them both from Java, but being natively Scala libraries, you are really better off switching to Scala if you are going to use them.
- zackangelo 12y agoIndeed, the Akka team published an blog post [1] a while back that demonstrates superior performance versus a traditional thread pool. The actor model seems to be a very favorable use case for F/J though. [1] http://letitcrash.com/post/17607272336/scalability-of-fork-join-pool http://letitcrash.com/post/17607272336/scalability-of-fork-j...