Gemini 4 Carbon takes nearly an hour on bug fixes that Opus and Astra finish in minutes
Why is Gemini 4 Carbon taking so long?

Kernel benchmarked Gemini 4 Carbon on private bug-fixing evals and found it took close to an hour where Opus and Astra took minutes. Tracing every step, they attribute the gap to slower inference (16–30% versus Astra), roughly half of Carbon's steps going to work the ticket never asked for, and mechanical inefficiencies like single-file reads and re-reading 39% of lines it had already seen. Injecting a periodic "do you have enough to fix it?" check-in cut one trial from 37 to 28 minutes.
This implies that the slowness seems to come from how Carbon behaves, not what it knows.
- tristanj
It's pretty obvious that Gemini 4 Carbon is not token efficient. It also has relatively low tokens-per-second compared to other models. I can think of several reasons why this is the case:
1. Google has huge amounts of cash and compute. Their goal was to train a model that that has the highest quality & frontier performance, not create a model that's efficient to run and serve. They have other models for that, like Hydrogen.
2. Google created Carbon without caring for inference costs. DeepMind is subsidized by the rest of Google's empire. Selling inference is an insignificant part of Google's revenue. But for Anthropic and OpenAI, selling inference is their entire business model. Anthropic and OpenAI have enormous incentive to sell as much inference as they can in the most efficient manner. Google doesn't have this incentive.
3. They are one of the few companies that can be inefficient. Out of all the frontier labs, Google DeepMind is probably the least constrained by compute. Chinese labs have around 10 to 100 times less compute, so they must release highly optimized models.
- horacemorace
I was just using this one today for some coding tinkering and it was super slow. But the way it solves problems with a light touch while still driving toward sensible architecture is refreshing after claude’s bulldozer attitude. It was able to integrate repeated creeping scope nicely with what it had already done. Very different feel than sonnet/opus, and even gemini 3.8.
- hetspookjee
Might be the only one in the thread but ever since Gemini 4 Argon. I’ve become a huge fan of the Google models. I do use Carbon most of the time since it’s become available but notice that i also am falling back more and more on Argon again without much difference. For security purposes argon has far fewer triggers.
I only use the Google models as orchestrator for how they talk and analyse. I let it delegate everything to Astra / Fable / Opus models
- bagacrap
This part actually seems like a feature:
> Unnecessary work. About half of Carbon's steps went on work the tickets never asked for: auditing code the fix didn't need and closing loopholes the ticket had already ruled out.
I have anecdotally noticed this, but I thought of it as Carbon "thinking" more "deeply" about the implications of a change. That can be a good thing! Instead of just doing exactly what I ask it, it is able to flag new bugs in far away code that would result, and it's able to find very subtly dead code in large codebases during redactors. My daily driver is Sol, which is exceedingly fast but is relatively focused on the task at hand. I think of my collection of models as similar to a team of humans who all have their strengths and weaknesses, and I'm much more likely to ask Carbon to review some work I've done than to help enact my ideas in the first place.
- lmeyerov
It's been jarring & confusing to go from a year and a half of Claude Code max plan, and equivalent of Codex, to Google agy & their models
My flow is roughly a few days to max out Claude sub, a few days to max out codex, and 1 afternoon to max out agy
While Astra/fable, sol/opus, sonnet/Luna are largely interchangeable when jumping codex vs Claude Code on the same repo+skills... that hasn't been true when using agy with Google models
My next stop may be drop agy harness in favor of codex/opencode to see if the models are fine and agy is the problem
- timtam
Using it through the prompt box, I kept running into 500 INTERNAL (TURN_STEPS_EXCEEDED).
Gemini couldn’t finish this response
I’m sorry, this request needed too many steps to finish in time. Please try asking a more specific question, or break it into smaller requests.
I only got around the issue by strictly setting an effort budget or a stopping rule.
- Lerc
A Theo vid suggests there's a time to first token issue. When doing subagent actions it can compound to be massive from a bunch of internal short queries.
It really looks like something is broken more than just being inefficient.
- dada216
ITT it's that huge max output token of 1mln tokens.
It's pretty far beyond other models (Opus 5.5 is at 128k).