[
https://issues.jboss.org/browse/WFCORE-1530?page=com.atlassian.jira.plugi...
]
David Lloyd commented on WFCORE-1530:
-------------------------------------
It's worth noting though that unless you have very long running operations, a lower
thread count might be acceptable for WildFly with Undertow because its task dispatch model
is fundamentally different.
It should be possible to provide a 'per-cpu' value when
configuring the task-max-threads attribute of a worker
--------------------------------------------------------------------------------------------------------------
Key: WFCORE-1530
URL:
https://issues.jboss.org/browse/WFCORE-1530
Project: WildFly Core
Issue Type: Enhancement
Affects Versions: 2.1.0.Final
Reporter: Juan AMAT
Assignee: Tomaz Cerar
We have an application running under JBoss EAP 6.4 and we are in the process to make it
also run under Wildfly.
While doing performance testing we noticed that the number of threads that can process
the incoming http requests was way lower in Wildfly.
Indeed we were using the 'default' worker and by default the max threads is set
to 16 times the cpu count. In Jboss EAP the default configuration is 512 times the cpu
count.
We were hitting this max and we did increase it. But then we had to provide an absolute
value (and we would need to provide different values per type of servers).
It will be nicer to be able to configure instead a per-cpu value.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)