跳到正文
Hacker News· deenadz·· 4 小时前AI 评分38

为什么 Gemini 4 Carbon 这么慢?

Why is Gemini 4 Carbon taking so long?

AI 导读

对比试验显示,GPT-6 Astra 在 1 分钟内定位 bug 并在 3 分钟后写出修复,Gemini 4 Carbon 约 6 分钟定位原因,却再过 25 分钟才开始写代码。在每 5 轮自动注入“是否已有足够信息修复”检查的改进测试框架下,Carbon 完成时间从 37 分钟降至 28 分钟,定位到动手之间的间隔从 25 分钟缩至约 10 分钟,说明其缓慢源于行为习惯而非知识缺口。

正文

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 · kernel.dev