Hi Mark,
Thanks for the detailed reply. I think I get it now.
The problem I was trying to solve was to dynamically control the
concurrency/in-flight requests (requests being processed by worker threads
+ requests in queue) based on the response times of requests (time spent in
queue + time spent
On 09/05/2020 14:08, Vikas Kumar wrote:
> I did not know about the images being dropped.
>
> Here are the steps I depicted in the image:
>
> Step 0: Request accepted by OS
> Step 1: Request sent to Tomcat. Tomcat accepts the request if it's internal
> queue is not full, else rejects the request
>
On Sat, 9 May 2020 at 9:09 PM, Vikas Kumar wrote:
> I did not know about the images being dropped.
>
> Here are the steps I depicted in the image:
>
> Step 0: Request accepted by OS
> Step 1: Request sent to Tomcat. Tomcat accepts the request if it's internal
> queue is not full, else rejects the
I did not know about the images being dropped.
Here are the steps I depicted in the image:
Step 0: Request accepted by OS
Step 1: Request sent to Tomcat. Tomcat accepts the request if it's internal
queue is not full, else rejects the request
Step 2: Tomcat adds the request to the queue if all wor
On Sat, May 9, 2020, 07:16 Vikas Kumar wrote:
> As per my understanding (using a Spring Boot app with Tomcat server), we
> define:
>
>- Max no. of worker threads (maxThreads, default 200)
>- Tomcat queue size (maxConnections, default 8192 for APR, 1 for
>NIO). When all worker thre
As per my understanding (using a Spring Boot app with Tomcat server), we
define:
- Max no. of worker threads (maxThreads, default 200)
- Tomcat queue size (maxConnections, default 8192 for APR, 1 for
NIO). When all worker threads are busy, requests are placed into the queue.
As wor
