Whether to use invokeAll or submit – java Executor service

by

Option 1 : You are submitting the tasks to ExecutorService and you are not waiting for the completion of all tasks, which have been submitted to ExecutorService

Option 2 : You are waiting for completion of all tasks, which have been submitted to ExecutorService.

What should be the preferred way?

Depending on application requirement, either of them is preferred.

  1. If you don’t want to wait after task submit() to ExecutorService, prefer Option 1.
  2. If you need to wait for completion of all tasks, which have been submitted to ExecutorService, prefer Option 2.

Is there any disadvantage or performance impact in any of them compared to the other one?

If your application demands Option 2, you have to wait for completion of all tasks submitted to ExecutorService unlike in Option 1. Performance is not criteria for comparison as both are designed for two different purposes.

And one more important thing: Whatever option you prefer, FutureTask swallows Exceptions during task execution. You have to be careful. Have a look at this SE question: Handling Exceptions for ThreadPoolExecutor

With Java 8, you have one more option: ExecutorCompletionService

A CompletionService that uses a supplied Executor to execute tasks. This class arranges that submitted tasks are, upon completion, placed on a queue accessible using take. The class is lightweight enough to be suitable for transient use when processing groups of tasks.

Have a look at related SE question: ExecutorCompletionService? Why do need one if we have invokeAll?

More Related Contents:

  1. ExecutorCompletionService? Why do need one if we have invokeAll?
  2. How to wait for all threads to finish, using ExecutorService?
  3. ExecutorService that interrupts tasks after a timeout
  4. Synchronization vs Lock
  5. Executors.newCachedThreadPool() versus Executors.newFixedThreadPool()
  6. How to properly use Java Executor?
  7. What are the advantages of using an ExecutorService?
  8. Java’s Fork/Join vs ExecutorService – when to use which?
  9. Impossible to make a cached thread pool with a size limit?
  10. ThreadPoolExecutor Block When Queue Is Full?
  11. Java ExecutorService: awaitTermination of all recursively created tasks
  12. What is adaptive spinning w.r.t lock acquisition?
  13. Run Java Threads sequentially
  14. FixedThreadPool vs CachedThreadPool: the lesser of two evils
  15. WAITING at sun.misc.Unsafe.park(Native Method)
  16. ThreadPoolExecutor Block When its Queue Is Full?
  17. Java: ExecutorService that blocks on submission after a certain queue size [duplicate]
  18. How to pause/resume all threads in an ExecutorService in Java?
  19. Future task of ExecutorService not truly cancelling
  20. Java 8: Parallel FOR loop
  21. Controlling Task execution order with ExecutorService
  22. Why must wait() always be in synchronized block
  23. How to share data with two(2) SwingWorker class in Java
  24. Volatile vs Static in Java
  25. Convert from List to CompletableFuture
  26. Choose between ExecutorService’s submit and ExecutorService’s execute
  27. How to use invokeAll() to let all thread pool do their task?
  28. Writing long and double is not atomic in Java?
  29. Thread Confinement
  30. ExecutorService vs Casual Thread Spawner

Leave a Comment