It is written in different sources that ThreadPool is more often used for short-live asynchronous tasks. But I have much faster tasks on my computer with SimpleAsyncTaskExecutor. Maybe I incorrectly configure ThreadPool? Who worked with this? Help is needed.

I'm just doing a series of tasks - parsing different external pages.

  • According to the documentation, SimpleAsyncTaskExecutor launches a new Thread for each task (by default, in unlimited quantities), and ThreadPoolTaskExecutor - several ( corePoolSize by default - 1). So you are probably right. - zRrr
  • @zRrr, I put a large corePoolSize and max but somehow it didn’t help me much - vkovalchuk88
  • try to put the size of the thread pool by the number of available cores - the effect should be better. No queues will be superfluous, nor downtime of the nuclei. - DimXenon
  • one
    @DimXenon, it works very slowly. SimpleAsyncTaskExecutor is much faster. - vkovalchuk88
  • @DimXenon, apparently, there will be more extra queues! - vkovalchuk88

0