You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by yogesh hingmire <yo...@gmail.com> on 2013/01/18 18:54:29 UTC

TomCat Executor

Folks,

What are the performance implications of not using the executor element
(threadpool) for my AJP connector ?

The threads will not be pooled and a new thread will be created for every
request that will be serviced, taking down the performance ?
(Essentially no thread Pooling)

Is my understanding correct ?

I am all for pooling dont get me wrong.

Thank You

Re: TomCat Executor

Posted by Daniel Mikusa <dm...@vmware.com>.
On Jan 18, 2013, at 3:08 PM, yogesh hingmire wrote:

> Thanks Dan,
> 
> So when i am not using the executor and specifying the maxthreads in the
> connector element, what would be the size of the pool ?

maxThreads

From the docs...

"The maximum number of request processing threads to be created by this Connector, which therefore determines the maximum number of simultaneous requests that can be handled. If not specified, this attribute is set to 200. If an executor is associated with this connector, this attribute is ignored as the connector will execute tasks using the executor rather than an internal thread pool."

  https://tomcat.apache.org/tomcat-7.0-doc/config/http.html#Standard%20Implementation

Dan


> 
> Yogesh
> 
> On Fri, Jan 18, 2013 at 12:04 PM, Daniel Mikusa <dm...@vmware.com> wrote:
> 
>> On Jan 18, 2013, at 12:54 PM, yogesh hingmire wrote:
>> 
>>> Folks,
>>> 
>>> What are the performance implications of not using the executor element
>>> (threadpool) for my AJP connector ?
>> 
>> Instead of having one pool of threads that you can share across multiple
>> connectors, you'll just have one pool of threads specific to one connector.
>> If you have multiple connectors sharing a pool of threads it may be more
>> efficient, depending on your applications and server load.
>> 
>>> 
>>> The threads will not be pooled and a new thread will be created for every
>>> request that will be serviced, taking down the performance ?
>>> (Essentially no thread Pooling)
>> 
>> No. Threads are pooled whether you specify an executor or not.
>> 
>> Dan
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>> 
>> 

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Re: TomCat Executor

Posted by yogesh hingmire <yo...@gmail.com>.
Thanks Dan,

So when i am not using the executor and specifying the maxthreads in the
connector element, what would be the size of the pool ?

Yogesh

On Fri, Jan 18, 2013 at 12:04 PM, Daniel Mikusa <dm...@vmware.com> wrote:

> On Jan 18, 2013, at 12:54 PM, yogesh hingmire wrote:
>
> > Folks,
> >
> > What are the performance implications of not using the executor element
> > (threadpool) for my AJP connector ?
>
> Instead of having one pool of threads that you can share across multiple
> connectors, you'll just have one pool of threads specific to one connector.
>  If you have multiple connectors sharing a pool of threads it may be more
> efficient, depending on your applications and server load.
>
> >
> > The threads will not be pooled and a new thread will be created for every
> > request that will be serviced, taking down the performance ?
> > (Essentially no thread Pooling)
>
> No. Threads are pooled whether you specify an executor or not.
>
> Dan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>

Re: TomCat Executor

Posted by Daniel Mikusa <dm...@vmware.com>.
On Jan 18, 2013, at 12:54 PM, yogesh hingmire wrote:

> Folks,
> 
> What are the performance implications of not using the executor element
> (threadpool) for my AJP connector ?

Instead of having one pool of threads that you can share across multiple connectors, you'll just have one pool of threads specific to one connector.  If you have multiple connectors sharing a pool of threads it may be more efficient, depending on your applications and server load. 

> 
> The threads will not be pooled and a new thread will be created for every
> request that will be serviced, taking down the performance ?
> (Essentially no thread Pooling)

No. Threads are pooled whether you specify an executor or not.

Dan

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org