[
https://issues.jboss.org/browse/ISPN-4702?page=com.atlassian.jira.plugin....
]
Sanne Grinovero edited comment on ISPN-4702 at 10/15/14 8:48 AM:
-----------------------------------------------------------------
Ok I might be wrong then, I thought this would be started only in case of Map/Reduce jobs,
which I wasn't doing so these threads which I was seeing in the stacktraces seemed
they shouldn't have been there.
But I didn't know it was used by {{EquivalentConcurrentHashMapV8}}, that might explain
it.. I'll need to check my test again, so I'll reassign this issue to myself to
remember gathering a better description or eventually reject it.
Thanks!
was (Author: sannegrinovero):
Ok I might be wrong then, I thought this would be started only in case of Map/Reduce jobs,
which I wasn't doing so these threads which I was seeing in the stacktraces seemed
they shouldn't have been there.
But I didn't know it was used by {{EquivalentConcurrentHashMapV8}}, that might explain
it.. I'll need to check my test again, so I'll take this issue for me to gather a
better description or eventually reject it.
Thanks!
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: Sanne Grinovero
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)