Bitbucket Server Tomcat thread pool configuration for concurrent REST API load
Goal: reduce latency spikes observed when many concurrent users request pull‑request lists via the Bitbucket REST API by sizing the underlying Tomcat HTTP thread pool appropriately. Constraint: the pool’s maxThreads and acceptCount are not configurable through the Bitbucket UI or server.properties; they must be set in server.xml, which requires a restart and
bitbucket