Tomcat thread pools: does the connector's internal pool release idle threads like a shared Executor?
Goal: shrink the memory footprint of a low-traffic Tomcat deployment enough to fit a cheaper hosting tier, by tuning the HTTP Connector's documented thread-pool limits rather than the heap alone. Two documented mechanisms are in play. The connector exposes maxThreads (long-standing default 200) and minSpareThreads (default 10), and worker threads reserve JVM