Unverified50% confidenceReleaseExact time
Version 2.0.3 changed the circuit-breaker rejection response to carry the `x-should-retry: false` and `Retry-After` headers, so that rejected requests return in about 1 millisecond instead of 1.35 seconds, and p95 dropped from 1459 milliseconds to 314 milliseconds.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/18/2026
First Seen
Valid until: 1/16/2027
Sources
Related Entities
Related Claims
UnverifiedIn 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.72% similarUnverifiedgg-friggin-ez has a response latency of less than 500 milliseconds.68% 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.67% similarUnverifiedWith the 4096 MiB and 4-slot configuration, small reads within a session increased from a clean 0.07 seconds to an extra 0.15 to 0.35 seconds per turn; after dropping to 3072 MiB and 3 slots, the occasional tail latency returned to near the original level.67% similarUnverifiedMaximem Synap claims a P75 recall latency of under 15 milliseconds66% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1060941API
curl https://kongchang.com/api/v1/knowledge/claims/1060941MCP
get_claim(id=1060941)