Async Data Fetch vs Thread Pool Tuning: Which Better Controls Latency for Concurrent Requests in Jira Align?

Goal: Minimize response latency when many users interact with Jira Align at the same time.

Uncertainty: Two documented configuration options—enabling asynchronous data fetching and adjusting the thread‑pool size—are available, but there is limited guidance on how each affects latency under high concurrent load or whether they can be combined safely.

Which option yields the greater latency reduction under peak concurrent request volume? Are there any known side effects or limits when applying both options simultaneously?