Live data from Hacker News

I ran Gemma 4 as a local model in Codex CLI

blog.danielvaughan.com

61–70 of 123 posts

Re: I ran Gemma 4 as a local model in Codex CLI

#61
post #10

For coding it makes no sense to use any quantization worse than Q6_K, from my experience. More quantized models make more mistakes and if for text processing it still can be fine, for coding it's not.

I don't think most people realize that. Quality of tokens beats quantity of token. I always tell folks to go as high a quant as you can only go lower if you just don't have the memory capacity.

what do you mean with that, I’m not sure I understood what you said

Re: I ran Gemma 4 as a local model in Codex CLI

#62
post #12

> The finding I did not expect: model quality matters more than token speed for agentic coding. I'm really surprised how that was not obvious. Also, instead of limiting context size to something like 32k, at the cost of ~halving token generation speed, you can offload MoE stuff to the CPU with --cpu-moe.

Why would token speed matter for anything other than getting work done faster? It's in the name - "speed".

Re: I ran Gemma 4 as a local model in Codex CLI

#63

Earlier quoted context omitted.

I don't think most people realize that. Quality of tokens beats quantity of token. I always tell folks to go as high a quant as you can only go lower if you just don't have the memory capacity.

what do you mean with that, I’m not sure I understood what you said

Better go for a less-quantized model even if it's slower than go for a faster, quantized one.

Re: I ran Gemma 4 as a local model in Codex CLI

#64

"The reason I had not done this before is that local models could not call tools. " Rubbish, we have been calling tools locally for 2 years, and it's very false that gemma3 scored under 7% in tool calling. Hell, I was getting at least 75% tool calling with llama3.3

This entire article reads like AI slop anyway.

I also recommend anyone with a GB10 device to go try out the spark-vllm-docker setup, and check the Nvidia GB10 forums for the recently released optimised Qwen 3.5 122B A10B setup: 50tk/s is quite impressive for a decent local model!

Re: I ran Gemma 4 as a local model in Codex CLI

#65
post #27
post #9

I'm currently experimenting with running google/gemma-4-26b-a4b with lm studio ( https://lmstudio.ai/ ) and Opencode on a M3 Ultra with 48Gb RAM. And it seems to be working. I had to increase the context size to 65536 so the prompts from Opencode would work, but no other problems so far. I tried running the same on an M3 Max with less memory, but couldn't increase the context size enough to be useful with Opencode. I…

I do the same thing on a MacBook Pro with an M4 Max and 64GB. I had problems until the most recent LM Studio update (0.4.11+1), tool calling didn't work correctly. Now both codex and opencode seem to work.

Which do you prefer? And what lmstudio api works best for these tools?

Re: I ran Gemma 4 as a local model in Codex CLI

#66

Gemma 4 is a strongly censored model, so much so that it refused to answer medical and health related questions, even basic ones. No one should be using it, and if this is the best that Google can do, it should stop now. Other models do not have such ridiculous self-imposed problems.

Since it's open weights there's nothing stopping you from grabbing one of the uncensored variants from huggingface.co

Re: I ran Gemma 4 as a local model in Codex CLI

#67

Earlier quoted context omitted.

I don't think most people realize that. Quality of tokens beats quantity of token. I always tell folks to go as high a quant as you can only go lower if you just don't have the memory capacity.

what do you mean with that, I’m not sure I understood what you said

AI models like gemma4 are available in different quant "sizes", think about it as an image available in various compression levels.

The best image is the largest, takes up the most memory when loading, and while it is large and looks the best, it uses up much of your system resources.

On the other end of the spectrum there is a smaller much more compressed version of that same image. It loads quickly, uses less resources, but is lacking detail and clarity of the original image.

AI models are similar in that fashion, and the parent poster is suggesting you use the largest version of the AI model your system can support, even if it runs a little slower than you like.

Re: I ran Gemma 4 as a local model in Codex CLI

#69
post #9

I'm currently experimenting with running google/gemma-4-26b-a4b with lm studio ( https://lmstudio.ai/ ) and Opencode on a M3 Ultra with 48Gb RAM. And it seems to be working. I had to increase the context size to 65536 so the prompts from Opencode would work, but no other problems so far. I tried running the same on an M3 Max with less memory, but couldn't increase the context size enough to be useful with Opencode. I…

I have a similar setup. It might be worth checking out pi-coding-agent [0].

The system prompt and tools have very little overhead ([0] https://www.npmjs.com/package/@mariozechner/pi-coding-agent#...

Re: I ran Gemma 4 as a local model in Codex CLI

#70

Gemma 4 is a strongly censored model, so much so that it refused to answer medical and health related questions, even basic ones. No one should be using it, and if this is the best that Google can do, it should stop now. Other models do not have such ridiculous self-imposed problems.

There are uncensored / "abliterated" / heretic versions available on Huggingface.
Post reply on HN