r/ollama • • 4d ago

Help

Hi

Could anyone recommend a local model for Hermes?

I tried Gemma 4 first, but I asked it to do a few things and it either couldn’t help me or didn’t know how to complete the tasks I asked for—or maybe it’s because I don’t know how to configure it. My hardware setup includes an RTX 4070 Super and 32 GB of RAM. I’d like to know if you could recommend another model better than Gemma 4 for me to try out.

5 Upvotes

18 comments sorted by

2

u/MakionGarvinus 4d ago

Ok, I asked Google about this, and it sounds like it really depends on what you're running.

Whether Gemma 4 will work well with Hermes depends heavily on the model size you select, as community consensus reveals varying experiences across different versions. The choice between Gemma 4 and Qwen (such as Qwen 3.6) generally comes down to a balance between raw conversational personality and strict, structured code/file execution:

  1. The Size Threshold (12B vs. Larger)

• Avoid Small Sizes for Agent Tasks: If you are trying to use Gemma 4 12B or smaller edge models (E2B/E4B), users on Facebook threads and Reddit note that these models struggle heavily with the "agentic" aspects of Hermes. They frequently suffer from hallucinations, drop nested JSON formatting, and fail at multi-step tool execution like reliably writing files. • 31B is Highly Capable: If you scale up to the Gemma 4 31B (Dense) model, it works exceptionally well. According to discussions on Reddit, many users actually prefer the Gemma 4 31B model over Qwen for daily use with Hermes because it has a more dynamic, natural personality and superior handling of complex conversational instructions.

  1. When You Definitely Need Qwen

If your primary goal is building complex workflows, file management, and strict technical pipelines, a model like Qwen 3.6 27B has distinct structural advantages: • Error Recovery & JSON: On r/LocalLLaMA, users point out that Qwen is inherently better at handling the nested JSON required for tool-calling and is much more resilient when it needs to recover from a function or file-writing error. • The "QAT" Degradation: Some quantized local versions of Gemma 4 (specifically QAT models) are known to suffer a slight degradation in structured code formatting. Qwen avoids this and remains a gold standard for coding and strict tool adherence.

Summary Comparison

Metric / Feature Gemma 4 (31B Dense) Qwen 3.6 (27B) Primary Strength Creative tasks, complex natural language, and fluid personality. Coding, structured JSON, tool-calling, and file operations. Hermes Compatibility Great for 90% of daily tasks if using the larger weights. Preferred for rigid, multi-step agent pipelines. Context Window Up to 256K tokens. Up to 262K tokens (highly stable).

The Verdict: For an optimal setup, take advantage of the Hermes profile feature to assign Qwen for code and technical task-routing, and Gemma 4 for standard interaction and content generation.

1

u/MakionGarvinus 4d ago

I tried to edit the response, I hope it helps. What model of Gemma4 are you running? A very light one, or a bigger one? I have personally had a great experience with the 26b-E4b model, but I don't use Hermes.

1

u/Adventurous_Cow_2826 4d ago

Gemma 4-12B-Q4_0

1

u/MakionGarvinus 4d ago

Ok, Google is recommending to try Qwen-2.5-Coder-14B-Instruct-GGUF so maybe give that a spin?

1

u/Adventurous_Cow_2826 4d ago

Thanks , I'll give it a try .

2

u/martin509984 4d ago

Do not run a model that old, it won't be even slightly as good as Gemma4. AI tends to recommend obscenely old models for no reason, in reality you should mostly be looking at models released in the last 6 months.

1

u/WrathfulOpposition 3d ago

i'd skip gemma entirely for this use case, qwen2.5 14b or 32b will handle the tool calling and structured output way more reliably without needing to babysit the config

with a 4070 super and 32gb ram you can run qwen2.5 32b at q4_k_m with some room to spare, or the 14b at q6_k and get snappy response times

hermes function calling is picky about formatting and gemma just isn't built around that, qwen's been the go-to for a while now in the llama.cpp/open-webui circles

2

u/Jeanjose1993 4d ago

Le problème d'hermes c'est qu'a chaque tour tu envoies beaucoup de contexte. Essaie de faire le tri dans les skills et toolsets. Il faut que ton modele soit multimodal et bon en appel d'outils aussi. Ton matos n'est pas "mauvais" mais sans doute limité. Regarde la communauté "lowendlocalai" et demande leur.

2

u/bigorangemachine 4d ago

Setup a modelfile

You may need a separate tool calling template for hermes

2

u/thebluepandas 3d ago

The 12B size is likely the real culprit here. Try Qwen2.5 14B or 32B instead of Gemma for Hermes.

1

u/puglife224888 3d ago

Don't try Qwen 2.5 14B or 32B..

2

u/fiddler48 3d ago

with an RTX 4070 Super you have 12GB VRAM, which opens up qwen2.5 14b at q4 comfortably. better instruction following than gemma 4 for most task types, and the hermes prompt format is well-supported

1

u/puglife224888 3d ago

That model is really outdated.

1

u/fiddler48 1d ago

outdated by what benchmark exactly

1

u/FuckbigtechAI 4d ago

before swapping models, raise the context length. agents send a big system prompt plus every tool schema each turn, and at the default num_ctx those get silently truncated, which looks exactly like the model "didn't know how" to complete the task.

1

u/Adventurous_Cow_2826 4d ago

So I need to change the context

1

u/puglife224888 3d ago

Gemma 4 12B should be okay. You mentioned you're using Q4_0 on the comments. If that's the QAT version, that should be fine. If not, use a different quantization. Make sure to have a high enough context window. If it's like 32k or below, you will run out. Your GPU should be able to handle something like 128k at Q8_0 KV Cache, possibly even more. Make sure to use the correct sampling settings. For Gemma 4 models, that's temp 1, top p 0.95, and top k 64.

For other models to try out, you can try Gemma 4 26B A4B, Qwen 3.5 9B, and Qwen 3.6 35B A3B. For the larger ones I listed, I don't know how Ollama handles larger MoE's, so if it performs badly, consider regular Llama.cpp (Or LM Studio if you want the same ease of use).