[jboss-jira] [JBoss JIRA] (WFLY-4653) Weld thread pool should be wildfly global
Jozef Hartinger (JIRA)
issues at jboss.org
Thu May 21 04:06:19 EDT 2015
[ https://issues.jboss.org/browse/WFLY-4653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jozef Hartinger moved WELD-1953 to WFLY-4653:
---------------------------------------------
Project: WildFly (was: Weld)
Key: WFLY-4653 (was: WELD-1953)
Affects Version/s: 9.0.0.CR1
(was: 2.2.6.Final)
Component/s: CDI / Weld
(was: Bootstrap and Metamodel API)
(was: Performance and Scalability)
(was: WildFly integration)
> Weld thread pool should be wildfly global
> -----------------------------------------
>
> Key: WFLY-4653
> URL: https://issues.jboss.org/browse/WFLY-4653
> Project: WildFly
> Issue Type: Enhancement
> Components: CDI / Weld
> Affects Versions: 9.0.0.CR1
> Reporter: Sebastian Maurer
>
> Weld keeps a thread pool for each deployment.
> Per default the pool is filled with "numProcessors" threads (see http://docs.jboss.org/weld/reference/latest/en-US/html/configure.html)
> When having many deployments, a single thread pool for the wildfly instance could improve the overall performance.
> This thread pool should be configurable in the weld subsystem of the wildfly configuration (e.g. standalone.xml).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
More information about the jboss-jira
mailing list