Tomcat Performance Tuning Guide: Core Components and Key Parameters

For applications that expose APIs using SpringBoot, Tomcat is the default servlet container. When traffic grows, simply scaling out may not be enough, so tuning Tomcat's configuration can boost performance without extra cost.

Component Architecture

Tomcat abstracts its functionality into Server, Service, Connector, and Container components. A Server can contain multiple Services; each Service can have multiple Connectors and a single Container. Connectors handle client connections (BIO, NIO, AIO) and forward requests to the Container's Engine, which delegates to Hosts, Contexts, and Wrappers that manage individual web applications and servlets.

Core Parameters

Understanding Tomcat's request processing flow—Connector receives a request, forwards it to Engine, which processes it and returns the result—highlights three key parameters for tuning:

acceptCount : Maximum number of connections the OS will accept when the thread pool is full and the Connector queue is at its limit.

maxConnections : Maximum number of connections the Connector queue can hold when all Container threads are busy.

maxThreads : Maximum number of request‑processing threads in the Container thread pool.

maxThreads

The default value in Tomcat 7/8 is 200. It should be calculated based on the ratio of I/O time to CPU time:

((IO time + CPU time) / CPU time) * CPU core count

This formula aims to keep CPUs busy while I/O is waiting. In practice, the computed value is often much larger than the number of CPU cores, but it should be validated with load testing because too many threads cause context‑switch overhead.

maxConnections

This defines how many connections the Connector can queue when all threads are occupied. A common practice is to set it equal to maxThreads , ensuring connections wait only briefly for a thread.

Lowering it slightly can reduce response time, but setting it too low may hurt throughput.

acceptCount

When both the thread pool and Connector queue are full, acceptCount limits how many additional connections the operating system will accept before rejecting new requests (default 100). It should not exceed maxConnections , otherwise many connections would remain unprocessed.

Adjusting this value can influence how quickly the OS hands off connections to Tomcat, especially with NIO/AIO where the OS can accept many connections.

Other Useful Parameters

connectionTimeout : Timeout for establishing a connection.

minSpareThreads : Minimum number of idle threads to keep alive, useful for handling traffic spikes.

Summary

The guide covered Tomcat's core components, explained the request‑handling flow, and detailed the three pivotal parameters—maxThreads, maxConnections, and acceptCount—along with tuning advice. Typically, maxThreads is derived from the I/O‑CPU formula and validated by stress testing; maxConnections is set to match maxThreads; acceptCount is kept similar to maxConnections but may be lowered to reduce latency.

By applying these adjustments, developers can improve Tomcat's throughput and response times without additional hardware.