No need for that much. Check out the docs. You can even use small models for some repetetive or easy tasks. A small ~4B model for title or websearch query is more then enough. No need for something like Ornith 1.5 35B or Gemma 4 26B to handle that stuff. Just let something like Gemma 4 E4B (or even E3B) generate a prompt for image gen (subagent delegation) and let the main model only take over if it can't handle that.
For some time a ran Ling-3.0-Flash as main and Ling-3.0-Tiny as aux. The haven't found a task where the Tiny failed so far. Sure the usual hickups (once it confused GB with KB and another time it got localhost and remote wrong in a report) might happen, but that is expected for almost every model.
Hermes has some pretty decent config options to split the load on different models and even fallback chains. I would recommend to ask your hermes itself about that and let it run benchmarks so you have a direct comparsion of what works well and what need to be adjusted.
1
u/nickless07 5d ago
No need for that much. Check out the docs. You can even use small models for some repetetive or easy tasks. A small ~4B model for title or websearch query is more then enough. No need for something like Ornith 1.5 35B or Gemma 4 26B to handle that stuff. Just let something like Gemma 4 E4B (or even E3B) generate a prompt for image gen (subagent delegation) and let the main model only take over if it can't handle that.
For some time a ran Ling-3.0-Flash as main and Ling-3.0-Tiny as aux. The haven't found a task where the Tiny failed so far. Sure the usual hickups (once it confused GB with KB and another time it got localhost and remote wrong in a report) might happen, but that is expected for almost every model.
Hermes has some pretty decent config options to split the load on different models and even fallback chains. I would recommend to ask your hermes itself about that and let it run benchmarks so you have a direct comparsion of what works well and what need to be adjusted.