[infinispan-issues] [JBoss JIRA] (ISPN-4702) The ForkJoin thread pool should be started lazily

[William Burns (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-4702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012014#comment-13012014 ] 

William Burns commented on ISPN-4702:
-------------------------------------

The ForkJoin javadocs do say

{quote}
A static {@link #commonPool()} is available and appropriate for most applications. The common pool is used by any ForkJoinTask that is not explicitly submitted to a specified pool. Using the common pool normally reduces resource usage (its threads are slowly reclaimed during periods of non-use, and reinstated upon subsequent use).
{quote}

So I would expect the threads if they were spawned to eventually be removed due to inactivity.

> The ForkJoin thread pool should be started lazily
> -------------------------------------------------
>
>                 Key: ISPN-4702
>                 URL: https://issues.jboss.org/browse/ISPN-4702
>             Project: Infinispan
>          Issue Type: Enhancement
>          Components: Distributed Execution and Map/Reduce
>    Affects Versions: 7.0.0.Beta1
>            Reporter: Sanne Grinovero
>            Assignee: Dan Berindei
>            Priority: Minor
>
> I'm not using these features, yet a significant amount of threads are being started.
> We should at least start this pool only on-demand, and ideally shut it down after a grace period if it's no longer being used.



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)