為甚麼 Gemini 4 Carbon 要花這麼久?
为什么“Gemini 4 Carbon”要花这么久?
測試顯示,Gemini 4 Carbon 延遲開始修正,似乎源於行為方式,而非不知道問題原因。每五輪加入一次確認後,Carbon 完成時間由 37 分鐘縮短至 28 分鐘,指出原因到開始編輯的等待時間則由 25 分鐘減至約 10 分鐘。相比之下,GPT-6 Astra 在指出原因後三分鐘便寫出修正。
Sample trial: time to find the cause vs. time to first edit
Minutes from the start of each run. GPT-6 Astra at max effort, Gemini 4 Carbon at high.
In this sample trial, both models identified the cause early, Astra within a minute and Carbon within about six. Astra had its fix written three minutes later; Carbon didn't write any code for another 25 minutes.
Carbon might not have been sure it had the cause (a knowledge gap), or it might have known and kept going anyway (a general habit, learned from training that rewards right answers more than it penalises extra steps). To tell them apart, we re-ran one of the trials in a modified harness that automatically injects the same check-in every five turns: "do you already have enough to make the fix?"
Sample trial with check-ins: time to find the cause vs. time to first edit
The same bug and scale as above. Gemini 4 Carbon at high, with the check-in injected every five turns (circles).
With check-ins, Carbon finished in 28 minutes instead of 37, and the wait between naming the cause and editing shrank from 25 minutes to about 10. This implies that the slowness seems to come from how Carbon behaves, not what it knows.
來源:Hacker News 熱門(buzzing.cc 中文翻譯) · kernel.dev