Issue Station
Sign In
Tools hereToolbox

hermes - 💡(How to fix) Fix Feature Request: VRAM-Aware Dynamic Task Routing

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
RAW_BUFFERClick to expand / collapse

The Problem: Currently, Hermes treats all tasks with the same resource allocation. On dual-GPU setups (like a 3090 Ti + 3090), simple tasks waste compute on high-precision (Q8) models, while complex tasks can bottleneck.

Proposed Solution: Introduce a hardware-aware routing layer that pings local VRAM levels. Simple tasks route to fast, small models; complex logic routes to primary high-parameter models.

Impact: Maximizes local hardware efficiency and prevents OOM crashes during multi-agent workflows.

Labels: enhancement, architecture, discussion

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#index setup#retrieval issue#search optimization#API routing#GPU setup

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING