[
https://issues.jboss.org/browse/JBRULES-3663?page=com.atlassian.jira.plug...
]
Mark Proctor updated JBRULES-3663:
----------------------------------
Assignee: Edson Tirelli (was: Mark Proctor)
Use a common thread pool for all TimerJobInstances
--------------------------------------------------
Key: JBRULES-3663
URL:
https://issues.jboss.org/browse/JBRULES-3663
Project: Drools
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Reporter: Sebastian Calbaza
Assignee: Edson Tirelli
From what I've seen(correct me if I'm wrong) there is, for each
StatefulKnowledgeSession a TimeManager -> JDKTimerService instances pair that use a
ScheduledThreadPoolExecutor of size one(default) for scheduling timer job instances.
Now the issues that I see are:
* not optimal resource utilization in case of large number of sessions
* number of sessions bounded by available memory for threads
* some performance penalty for concurrent jobs (I say some because all session ops are
serial)
I provided also a PR with to be reviewed
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira