News for hackers. Stuff that matters.
Re:Gemma 3 QAT Models: Bringing AI to Consumer GPUs by nico on Sunday April 20, 2025 @10:59AM (#43744205)
Been super impressed with local models on mac. Love that the gemma models have 128k token context input size. However, outputs are usually pretty short

Any tips on generating long output? Like multiple pages of a document, a story, a play or even a book?

Re:Gemma 3 QAT Models: Bringing AI to Consumer GPUs by simonw on Sunday April 20, 2025 @11:06AM (#43744252)
The tool you are using may set a default max output size without you realizing. Ollama has a num_ctx that defaults to 2048 for example: https://github.com/ollama/ollama/blob/main/docs/faq.md#how-c...
Re:Gemma 3 QAT Models: Bringing AI to Consumer GPUs by nico on Sunday April 20, 2025 @11:16AM (#43744320)
Been playing with that, but doesn’t seem to have much effect. It works very well to limit output to smaller bits, like setting it to 100-200. But above 2-4k the output seems to never get longer than about 1 page

Might try using the models with mlx instead of ollama to see if that makes a difference

Any tips on prompting to get longer outputs?

Also, does the model context size determine max output size? Are the two related or are they independent characteristics of the model?

Re:Gemma 3 QAT Models: Bringing AI to Consumer GPUs by simonw on Sunday April 20, 2025 @11:47AM (#43744532)
Interestingly the Gemma 3 docs say: https://ai.google.dev/gemma/docs/core/model_card_3#:~:text=T...

> Total output context up to 128K tokens for the 4B, 12B, and 27B sizes, and 32K tokens for the 1B size per request, subtracting the request input tokens

I don't know how to get it to output anything that length though.

Re:Gemma 3 QAT Models: Bringing AI to Consumer GPUs by nico on Sunday April 20, 2025 @12:14PM (#43744700)
Thank you for the insights and useful links

Will keep experimenting, will also try mistral3.1

Re:Gemma 3 QAT Models: Bringing AI to Consumer GPUs by Gracana on Sunday April 20, 2025 @03:43PM (#43746033)
You can probably find some long-form tuned models on HF. I've had decent results with QwQ-32B (which I can run on my desktop) and Mistral Large (which I have to run on my server). Generating and refining an outline before writing the whole piece can help, and you can also split the piece up into multiple outputs (working a paragraph or two at a time, for instance). So far I've found it to be a tough process, with mixed results.
Re:Gemma 3 QAT Models: Bringing AI to Consumer GPUs by nico on Sunday April 20, 2025 @05:28PM (#43746653)
Thank you, will try out your suggestions

Have you used something like a director model to supervise the output? If so, could you comment on the effectiveness of it and potentially any tips?

Re:Gemma 3 QAT Models: Bringing AI to Consumer GPUs by Gracana on Sunday April 20, 2025 @08:27PM (#43747588)
Nope, sounds neat though. There's so much to keep up with in this space.
Re:Gemma 3 QAT Models: Bringing AI to Consumer GPUs by Casteil on Sunday April 20, 2025 @11:39AM (#43744469)
This is basically the opposite of what I've experienced - at least compared to another recent entry like IBM's Granite 3.3.

By comparison, Gemma3's output (both 12b and 27b) seems to typically be more long/verbose, but not problematically so.

Re:Gemma 3 QAT Models: Bringing AI to Consumer GPUs by nico on Sunday April 20, 2025 @01:52PM (#43745278)
I agree with you. The outputs are usually good, it’s just that for the use case I have now (writing several pages of long dialogs), the output is not as long as I’d want it, and definitely not as long as it’s supposedly capable of doing
Re:Gemma 3 QAT Models: Bringing AI to Consumer GPUs by tootie on Sunday April 20, 2025 @08:00PM (#43747471)
I'm using 12b and getting seriously verbose answers. It's squeezed into 8GB and takes its sweet time but answers are really solid.