Looking for advice on handling rate limits when hitting the Script API endpoints during high-concurrency JMeter runs.
- Running JMeter 5.6.2 from Singapore to simulate 200 concurrent agents fetching dynamic scripts.
- Hitting 429 Too Many Requests on
GET /api/v2/scripts/{scriptId}after roughly 50 requests per second. - Current retry logic with exponential backoff is causing test timeouts and skewing throughput metrics.
- Is there a documented cache strategy or specific header to optimize for read-heavy script loads?