Unverified50% confidenceReleaseExact time
Version 2.0.3 fixed the bug where the server processed upstream calls serially and added the `--concurrency` parameter, which by default runs up to 16 upstream calls simultaneously; the same 20 distinct prompts completed in 3.0 seconds under default settings and in 1.5 seconds with `--concurrency 32`.
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 the provider-outage test, the direct-connection approach sent 89 calls to the dead provider within 60 seconds (30 requests each retried 3 times), whereas going through the proxy sent only 5 calls, a 94% reduction, because the circuit breaker opened after 5 consecutive failures.68% similarUnverifiedThe final solution for this Mini Program only performs brief synchronization at 5-second intervals within 15 seconds after the Mini Program is opened or operated, stopping after a maximum of three additional requests, at the cost of no longer maintaining second-level synchronization across multiple devices.68% similarUnverifiedTwo additional single runs were done to separate the variables: dropping agy's model to gemini-3.8-flash-low still took 332 seconds and 67 tool calls; switching to claude-opus-5-5-high, agy used only 51 seconds and 7 tool calls, close to Claude Code's 29 seconds.68% similarUnverifiedThe disadvantage of the leap smear technique is that the time on different servers at the same moment may differ by up to about 1 second.67% similarUnverifiedpromptfoo's first-run configuration took 25 minutes, running 40 data items took 3 minutes 12 seconds, the cost was $0.94, and the agreement rate with manual annotation was 34/40.66% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1060943API
curl https://kongchang.com/api/v1/knowledge/claims/1060943MCP
get_claim(id=1060943)