[
https://issues.apache.org/jira/browse/LENS-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431160#comment-15431160
]
Hudson commented on LENS-1277:
------------------------------
UNSTABLE: Integrated in Jenkins build Lens-Commit #1326 (See
[https://builds.apache.org/job/Lens-Commit/1326/])
LENS-1277 : Make threadpool sizes configurable for grizzly lens server (dbarr:
rev 6e4d1860aeb74e0ef9c85d13f653ee096f27458f)
* (edit) lens-server/src/main/java/org/apache/lens/server/LensServer.java
* (edit) lens-server/src/main/resources/lensserver-default.xml
* (edit) src/site/apt/admin/config.apt
* (edit)
lens-server-api/src/main/java/org/apache/lens/server/api/LensConfConstants.java
> Make threadpool sizes configurable for grizzly lens server
> -----------------------------------------------------------
>
> Key: LENS-1277
> URL: https://issues.apache.org/jira/browse/LENS-1277
> Project: Apache Lens
> Issue Type: Improvement
> Reporter: Deepak Barr
> Assignee: Deepak Barr
> Attachments: LENS-1277.2.patch
>
>
> By default, The number of configured worker threads while initializing a
> grizzly http server is 2*(no. of CPUs). In our systems, only 12 worker
> threads were available to serve the user requests which caused slow response
> times, with some requests taking more than 20 seconds. Reconfiguring the
> thread pool with core pool size of 40 and max pool size of 80 solved the
> problem for us.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
