forkjoinpool

Java 5 has introduced support for asynchronous task execution by a thread pool in the form of the Executor framework, whose heart is the thread pool implemented by java.util.concurrent.ThreadPoolExecutor. Java 7 has added an alternative thread pool in the form of java.util.concurrent.ForkJoinPool. Looking at their respective API, ForkJoinPool provides a superset of ThreadPoolExecutor's functionality in standard scenarios (though strictly speaking ThreadPoolExecutor offers more opportunities for tuning than ForkJoinPool). Adding to this the observation that fork/join tasks seem to be faster

Here's my understanding of the Stream framework of Java 8: Something creates a source Stream The implementation is responsible for providing a BaseStream#parallel() method, which in turns returns a Stream that can run it's operations in parallel. While someone has already found a way to use a custom thread pool with Stream framework's parallel executions, I cannot for the life of me find any mention in the Java 8 API that the default Java 8 parallel Stream implementations would use ForkJoinPool#commonPool() . ( Collection#parallelStream() , the methods in StreamSupport class, and others

We have three different multi threading techniques in java - Fork/Join pool, Executor Service & CountDownLatch Fork/Join pool ( http://www.javacodegeeks.com/2011/02/java-forkjoin-parallel-programming.html ) The Fork/Join framework is designed to make divide-and-conquer algorithms easy to parallelize. That type of algorithms is perfect for problems that can be divided into two or more sub-problems of the same type. They use recursion to break down the problem to simple tasks until these become simple enough to be solved directly. The solutions to the sub-problems are then combined to give a

I have a question about CompletableFuture method: public <U> CompletableFuture<U> thenApply(Function<? super T, ? extends U> fn) The thing is the JavaDoc says just this: Returns a new CompletionStage that, when this stage completes normally, is executed with this stage's result as the argument to the supplied function. See the CompletionStage documentation for rules covering exceptional completion. What about threading? In which thread this is going to be executed? What if the future is completed by a thread pool? The policies as specified in the CompletableFuture docs could help you