Unverified50% confidenceBenchmarkExact time
After optimization, the new round of M3.1 had an average response time of 16.11 seconds, but the long-tail problem remains unresolved.
1
Sources
50%
Confidence
Short-term (~14 days)
Relevance
10/24/2026
First Seen
Valid until: 11/7/2026
Sources
AI Protagonist Critiques Foundation Models: A Blind Test from a Product Perspective
bilibili波纳佩原住民10/23/2026
Related Entities
Related Claims
UnverifiedTesting the same scene and the same sentence 10 times each, DeepSeek's average response time was 3.68 seconds, M3's was 10.70 seconds, and pre-optimization M3.1's was as high as 20.35 seconds.80% similarUnverifiedRunning a 27B model on M1 Max with a 32,000-token prompt requires waiting more than 500 seconds before the first character is output, whereas the M5 Max takes less than one minute (approximately 40 seconds with optimized software).73% similarUnverifiedAplomb 1 对短问题的模型端计算时间约 15 毫秒，端到端延迟约 200 毫秒72% 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.71% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1092271API
curl https://kongchang.com/api/v1/knowledge/claims/1092271MCP
get_claim(id=1092271)