Fastest Servlets in the West?
summary
Tomcat behavior under load gets quantified: NIO vs APR connector shows APR more than doubles SSL throughput and keeps latency lower; enabling keep‑alive raises throughput roughly +250–300 RPS per connector. Tests use AB and JMeter load tests (50 clients typical, 500 for large files) and profilers like VisualVM and Java Mission Control to find hotspots. JVM idle heap ≈20–48 MB, a customer case shows 1,000,000 hourly requests ≈240 RPS; tuning connection pools and connector threads fixes the bottlenecks.
AI-written summary · about
chapters (11)
- 0:00Introduction and history
- 3:09Audience assessment
- 4:32Tomcat architecture
- 6:54Tuning focus areas
- 8:38JVM memory tuning
- 18:34Connector selection
- 23:36Performance testing
- 36:43Profiling application
- 40:29Application tuning demo
- 50:43Mission Control demo
- 58:37Best practices and QA
related talks
40mPreparing Spring Web Applications for Loom
38mProxing to tomcat with httpd
53mComet, Ajax, web browsers limitations and web apps performance factors
48mBetter performances on the server side with HTTP/2
01h 01mReactive web services
51mHitting the “refresh” button on your Spring web application
30mReactive Applications on Apache Tomcat and Servlet 3.1 Containers - Violeta Georgieva
52mBulletproof Java Enterprise Applications for The Hard Production Life