Unverified50% confidenceEventExact time
The measured timeline was: billing starts at 0 seconds, prefill CUDA graph capture completes at about 371 seconds (taking 287.7 seconds), /health returns 200 at 386.7 seconds, the first request completes at about 563 seconds (taking about 176 seconds), the second request completes at about 579 seconds, and billing stops at 639.6 seconds.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/12/2026
First Seen
Valid until: 1/10/2027
Sources
Related Entities
Related Claims
UnverifiedInitializing a CUDA context typically takes hundreds of milliseconds to several seconds, due to factors including device enumeration, firmware loading, PCIe bandwidth negotiation, and JIT kernel warm-up.71% similarUnverifiedOn its first run, after backfilling history, the scorer identified 263 one-hour stalls and two eleven-hour stalls; on a second-pass check, agents were actually working during about 108 points' worth of one-hour waits and those points were refunded; the two eleven-hour stalls were kept (the audit role was idle from 08:47 to 19:46 while the queue piled up).70% similarUnverifiedCopilot从停止输入到看到补全建议出现的整个链路通常在200-800毫秒之间完成70% similarUnverifiedIf the bill is split at the moment the health check passes (386.7 seconds), startup appears to account for 60%; but the first user actually gets an answer at about 563 seconds, by which point 88% of the bill has already been consumed.70% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1012425API
curl https://kongchang.com/api/v1/knowledge/claims/1012425MCP
get_claim(id=1012425)