DiffusionGemma: 4x Faster Text Generation
11–20 of 94 posts
Re: DiffusionGemma: 4x Faster Text Generation
#12A few days ago I was just thinking that Google never talked about their diffusion text generation model after demoing it at I/O a year ago. The rumor is that it was too expensive to run, but with the provided chart using the same 1x H100 hardware and comparing DiffusionGemma to regular Gemma, that shouldn't be the case. I'm curious what the downside for this speed is here aside from being slightly weaker than Gemma.
So the diffusion process takes more GFLOPs, if you have enough users you can already balance memory and compute.
Re: DiffusionGemma: 4x Faster Text Generation
#13Is the diffusion approach any use in Multi-Token Prediction (MTP) drafters? https://blog.google/innovation-and-ai/technology/developers-...
Re: DiffusionGemma: 4x Faster Text Generation
#14Is the diffusion approach any use in Multi-Token Prediction (MTP) drafters? https://blog.google/innovation-and-ai/technology/developers-...
Re: DiffusionGemma: 4x Faster Text Generation
#15Re: DiffusionGemma: 4x Faster Text Generation
#16We need more local open weight models that are performant and just as good (or good enough) as the best frontier ones. Then you will be able to achieve Jevons Paradox and enjoy the same “productivity gains” without paying for these extortionate token prices by closed model providers or have it as cheap as possible. And especially, no silent nerfing of the model.
Next year, and the year after, Fable, GPT 5.5 and Gemini 3.5 will feel quite ordinary. And perhaps even within reach of a prosumer running models locally.
Re: DiffusionGemma: 4x Faster Text Generation
#17A few days ago I was just thinking that Google never talked about their diffusion text generation model after demoing it at I/O a year ago. The rumor is that it was too expensive to run, but with the provided chart using the same 1x H100 hardware and comparing DiffusionGemma to regular Gemma, that shouldn't be the case. I'm curious what the downside for this speed is here aside from being slightly weaker than Gemma.
Well with a standard autoregressive model you can generate for example 256 tokens at once if you have 256 users, with this approach you can generate 256 tokens for a single user but you need several forward steps. So the diffusion process takes more GFLOPs, if you have enough users you can already balance memory and compute.
Re: DiffusionGemma: 4x Faster Text Generation
#18It is cool but local models while okay already feel noticeably worse than even the cheapest APIs so I can't see myself sacrificing even a little bit of their quality for speed. I'm sure it's worth it for some usecases, curious to hear specific ones that people are already planning to deploy to production.
Does not need opus level to write, and easy to iterate on.
Re: DiffusionGemma: 4x Faster Text Generation
#19Re: DiffusionGemma: 4x Faster Text Generation
#20It is cool but local models while okay already feel noticeably worse than even the cheapest APIs so I can't see myself sacrificing even a little bit of their quality for speed. I'm sure it's worth it for some usecases, curious to hear specific ones that people are already planning to deploy to production.
Maybe writing / bootstraping unit tests? Does not need opus level to write, and easy to iterate on.