What concurrent request threshold triggers LinkedIn's internal gateway to queue requests and cause latency spikes?

Determine the exact number of concurrent requests at which LinkedIn's internal gateway switches from immediate processing to temporary queuing, a behavior that adds observable latency distinct from rate‑limit throttling or client‑side connection‑pool exhaustion.

Public documentation only describes per‑application rate limits (e.g., 100 req/s) and does not disclose the adaptive concurrency control threshold, which may vary by region, account type, or specific API endpoint, making it difficult to isolate gateway‑induced latency in load‑test results.

What concurrent request level triggers the gateway queuing mechanism? How does this threshold change across different LinkedIn API products or geographic regions?