Unverified50% confidenceBenchmarkExact time
The latency data comes from a separate synthetic load: 4,096 document tokens and 50 questions. Q64's median cold-request latency is 2.237 seconds, versus 5.383 seconds for the native baseline and 56.872 seconds for the batched AnyJev configuration.
1
Sources
50%
Confidence
Short-term (~14 days)
Relevance
11/4/2026
First Seen
Valid until: 11/18/2026
Sources
Related Entities
Related Claims
UnverifiedThe demo output shows: requests spaced about one second apart rather than 0.5 seconds (Crawl-delay overrode the configuration), an exact 2-second wait on 429, a headless 503 getting about 1.1 seconds of jittered backoff, /private requests never leaving the local machine, and the last profile request hitting the daily cap midway through a retry.77% similarUnverifiedThe 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.76% similarUnverifiedSBC编解码器延迟约为150-200毫秒，aptX延迟约70毫秒，aptX Low Latency延迟可压缩至40毫秒以内75% similarUnverifiedTypeSafe AI Jev achieves latency comparable to regex on Qwen 1.7B (576.2 milliseconds vs 567.5 milliseconds, statistically verified t=8.138, p=1.38×10⁻⁹) while restoring recall to 65.7%.75% similarUnverifiedThe first-audio latency of ElevenLabs Realtime is 570 milliseconds (v1 Max version).72% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1134096API
curl https://kongchang.com/api/v1/knowledge/claims/1134096MCP
get_claim(id=1134096)