[
https://issues.jboss.org/browse/WFLY-1183?page=com.atlassian.jira.plugin....
]
Weixing Sun edited comment on WFLY-1183 at 5/28/13 3:22 AM:
------------------------------------------------------------
Hi Expert,
I have the performance comparison report in Weblogic appserver, and I got > 20%
performance boost, so I would like to continue this request.
detailed information would be enclosure in email.
Thanks again!
Weixing
was (Author: weixingsun):
Hi Expert,
I have the performance comparison report based on SPECjEnterprise2010 for the customized
thread pool feature in another appserver(Weblogic):
Apologize for delaying the reaction, since the performance environment need to be change
from JBoss to Weblogic, and tune the system to see the bottleneck on both the feature
enabled/disabled.
PASS 1800/2862/1.59 120/0/0/0/0/0/0 0.40/0.40 0.99/0.44/1.23 36/21/16/13/8 false
1mt-wls103-thread-disabled
PASS 2200/3486/1.58 20/40/9/14/50/1/50 0.53/0.53 1.64/0.55/1.32 42/24/17/18/11 false
1mt-wls103-thread-enabled
as above data shown, the customized thread pool feature could provide 400 more
InjectionRates, thus can provide more than 20% for this specific feature.
So, does this report provide enough evidence that could push the progress on this feature
request? Or please let me know if you want more detailed information I can provide.
Thanks again!
Weixing
Configure EJB3/MDB with an individual thread pool for each EJB.
---------------------------------------------------------------
Key: WFLY-1183
URL:
https://issues.jboss.org/browse/WFLY-1183
Project: WildFly
Issue Type: Feature Request
Components: EJB
Reporter: Jeremy Whiting
Assignee: jaikiran pai
For performance of an application to be scalable I need to configure sometimes a thread
pool to an EJB. The pool is not shared with other EJB in the deployed application.
For example
PoolA - EJB Dog
PoolB - EJB Cat
To configure this the ability no define the thread pool name for an EJB. Rather than an
EJB to the shared thread pool as it currently works.
--
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