Unverified50% confidenceBenchmarkExact time
After honoring retry-after and layering full jitter on top, the last call completed at 11.8 seconds, 313 requests were sent, and p95 was 9.1 seconds, with every metric better than the two backoff formulas.
1
Sources
50%
Confidence
Long-term
Relevance
10/19/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedThe full jitter strategy reduced p95 latency from 16.1 seconds to 10.5 seconds, but the last call completed at 17.1 seconds, and it sent 408 requests, 9% more than the fixed-delay strategy.78% similarVerifiedIn testing, the p99 latency per 160-millisecond tick was 147.4–147.5 milliseconds, with zero missed deadlines across three rounds totaling 84,000 session ticks measured.78% similarUnverifiedWhen a 429 is received, exponential backoff with random jitter should be implemented starting at about 500ms, and if a Retry-After response header is present, wait at least that long; ignoring Retry-After or retrying at fixed intervals will prolong the outage for the entire team.76% similarUnverifiedIf the P99 latency of a single service is 1 second, the probability that a call triggering 5 parallel sub-requests encounters at least one exceeding P99 latency is approximately 5% (1 - 0.99^5).76% similarUnverifiedThe retry loop in the code attempts at most 4 times, with exponential backoff starting at 500 milliseconds, and it prioritizes obeying the Retry-After response header when the service provides one.76% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1064749API
curl https://kongchang.com/api/v1/knowledge/claims/1064749MCP
get_claim(id=1064749)