ExecutorService vs ThreadPoolExecutor using LinkedBlockingQueue

Question

I am working on a multithreaded project in which I need to spawn multiple threads to measure the end to end performance of my client code, as I\'m doing Load and Performance

Answer 1

After 2 days of GC out of memory exception, ThreadPoolExecutor saved my life. :)

As Balaji said,

[..] one more advantage is with RejectionHandler.

In my case I had a lot of RejectedExecutionException and specifying (as follow) the discard policy solved all my problems.

private ThreadPoolExecutor executor = new ThreadPoolExecutor(1, cpus, 1, TimeUnit.SECONDS, new SynchronousQueue(), new ThreadPoolExecutor.DiscardPolicy());

But be careful! It works only if you don't need to execute all the threads that you submit to the executor.

For further information about ThreadPoolExecutor take a look at Darren's answer