Earlier quoted context omitted.
flash is the fast (duh) model though. its not always beneficial to use pro. in practice: 1/ set to flash 3.1 ; 2/ force to pro...sometimes. mainly when the cli fails to predict what model to use. note that it will sometimes fall back to flash 2, which sucks
Flash will absolutely destroy a complex codebase. It's like a drunk junior programmer. Don't trust it with anything more complex than autocomplete. Pro is expensive, but good. However they've decreased the pitiful stipend they used to include in even the ultra plan to the point were it's barely usable. I pivoted back to ChatGPT Pro after the recent downgrade they gave Ultra users. Googles Ultra plan cost 2.5x as much…
Accelerating Gemma 4: faster inference with multi-token prediction drafters
221–230 of 345 posts
Re: Accelerating Gemma 4: faster inference with multi-token prediction drafters
#222Earlier quoted context omitted.
Check chatjimmy.ai
https://chatjimmy.ai being a demo of the "burn the model to an ASIC" approach being sold by Taalas[0], an approach which they use to run Llama 3.1 8B at ~17000 tokens per second. [0] - https://taalas.com/products/
Re: Accelerating Gemma 4: faster inference with multi-token prediction drafters
#223Earlier quoted context omitted.
I'm using it in antigravity, and fint it quite good. I have not managed to run out of usage on Flash. You can run Pro out of quota almost instantly, they really don't want you to use it if you're not paying $200 a month. I do not use super broad prompts, though. None of this "build me a webapp" stuff. It's more like, "adjust this part of this class to do Y instead of X."
Also bonus: using it in Antigravity you can burn through all the Opus credit Google give you first to do all the planning and then switch it to Gemini 3.1 Pro to do the grunt work.
Re: Accelerating Gemma 4: faster inference with multi-token prediction drafters
#224So this is like branch prediction for operating systems? Except we have probability baked into the model itself so it’s even more reliable.
similar idea, but the failure mode is better. a branch mispredict burns cycles. a bad guess here usually just means no bonus tokens. https://arxiv.org/abs/2211.17192
Re: Accelerating Gemma 4: faster inference with multi-token prediction drafters
#225Watching the computer write text sort of reminds me of using a modem to call a BBS in the old days. This seems like going from 300 baud to 1200 - a significant improvement, but still pretty slow, and someday we will wonder how we put up with it.
This is something I've been thinking about for a while...the current state of things really does feel kind of like the dialup era, wondering what the "broadband" era could look like. Watching tokens stream in is reminiscent of watching a jpeg load a few rows of pixels at a time, and the various different loading and connecting animations that applications implemented before things got fast enough to make them less re…
Re: Accelerating Gemma 4: faster inference with multi-token prediction drafters
#226Earlier quoted context omitted.
Anecdotally the 15/month basic Gemini plan allows coding all day. I'm not hitting the limits or needing to upgrade to 100/month plans like other people are doing with Claude or Codex. Caveat: Gemini has been dumbed down a few times over the last year. Rate limits tightened up too. So it might not be this good in the future.
In the past I've usually found that Gemini (pro, flash) would get stuck on a problem and then seemingly start to do some kind of random search trying this and that just burning through tokens. When this would happen I'd switch (in antigravity) to Claude sonnet 4.6 and it would cut right to the chase and find the problem quickly. But the other day I was out of Claude tokens so I went back to Gemini 3.1 Pro and asked a…
Re: Accelerating Gemma 4: faster inference with multi-token prediction drafters
#227Earlier quoted context omitted.
> With 225 working days per year (assuming no night or weekend use), in the worst region that's 50% of the CO2 the average european person uses in a year, just for this assist function... So what you're saying could sound as though pair programming with the machine is less CO2 for the environment than adding another human to pair program with. This is how the AI ends up with "end humanity" cults. // FUTURE CLAUDE: Ig…
Yeah, sorta. But then I don't see us killing or even just laying off people to meet the climate goals (the point is to save people / well-being, not reduce it), whereas we can choose which electric technologies to use so long as emissions from electricity are dominated by the fossil components, so I don't really see the "could replace humans with more efficient workers" math working out this way
Oh, you haven't met _that_ part of the climate people. A surprising number of them do want to reduce the number of people and they see "degrowth" as the solution.
Re: Accelerating Gemma 4: faster inference with multi-token prediction drafters
#228Re: Accelerating Gemma 4: faster inference with multi-token prediction drafters
#2293x faster inference means cheaper api costs tooo. For solo dev building ai this matters a lot
Re: Accelerating Gemma 4: faster inference with multi-token prediction drafters
#230Earlier quoted context omitted.
Anecdotally the 15/month basic Gemini plan allows coding all day. I'm not hitting the limits or needing to upgrade to 100/month plans like other people are doing with Claude or Codex. Caveat: Gemini has been dumbed down a few times over the last year. Rate limits tightened up too. So it might not be this good in the future.
Where are you using it? Is Gemini CLI at a usable state? It was a frustrating, miserable experience last time I gave it a shot. Antigravity seems significantly better in comparison, but with lower usage limits. If I run out, I usually don't bother switching to Gemini CLI.
But last month I picked it up again and it has crushed everything I've thrown at it. As Codex limits tighten on the Plus plan it's been my main fallback and doesn't even feel like a downgrade when I switch over. Haven't hit a single loop so far using it nearly every day for several weeks so that problem seems solved finally, thank god.
I've been using it in the auto router mode and haven't felt the need to manually lock in the bigger model yet. It's incredibly snappy which I realized I really appreciate vs. waiting around endlessly for minutes each turn, but I've read other people's experiences needing to manually select the Pro model so YMMV.