Arshiya, On 9/28/20 12:58, Arshiya Shariff wrote: > With 200 threads(users) , ramp up duration of 2 seconds , loop count > 80 and by sending 1000 http2 requests/sec from JMeter Client to an > embedded tomcat application we did not observe any memory issue , but > on sending 1000 http2 requests/sec with 2000 or 1000 users from > JMeter , the application's heap space of 20 GB is occupied in 2 > minutes and after 2 full GCs the memory clears and comes down to 4GB > (expected) .
So a full GC releases the memory? > Embedded tomcat Version:9.0.38 > Max Threads : 200 > All other properties are the tomcat defaults. > > Why is tomcat not able to process many connections ? What evidence is there that Tomcat cannot process that many connections? You said above the only concern was used-heap space. If you have 200 threads, then you can only handle 200 active requests at a time. If you need to process 2000 requests *simultaneously*, then you need 2000 threads. If you only need 2000 *users* at the "same time", then 200 threads should be able to handle the load, depending upon the application's performance characteristics. > Why is the memory filled when the connections are increased, are > there any parameters to tune connections ? Are you using HttpSessions? -chris --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
