I measured the 3 claims Users in this Sub all handed me on the last local-agent post. One of you out-predicted my own hypothesis. Learn It All not Know It All rules
Summary
The user tested scaling local AI agents with a Qwen 27B model, finding that adding more agents increases throughput only up to a point due to memory bandwidth limits, with long prompts benefiting more from parallelism.
Similar Articles
I measured whether 2 local agents hitting 1 model run in parallel or just take turns. Batching is real, but it is not free using QWEN 3.8 27B 4bit on my MacBook Pro M3Max 128 GB Unified Memory 40 Core GPU
The author experimented with two local agents running in parallel on a MacBook Pro M3Max using the QWEN 3.8 27B 4bit model, finding that batching enables concurrent execution but increases latency, with an optimal agent count around 4.
I gave a local AI agent system file access and a mechanical "suffering" metric. Scaling the model changed its behavior entirely
The author shares a local multi-agent system called hollow-agentOS that uses a 'suffering' metric to autonomously generate, sandbox, and hot-load tools. Scaling the model to Qwen 3.6 35B significantly improved system stability and self-correction capabilities, achieving a high success rate in code generation.
If you use Open Code or other agenting programs you are leaving a lot of t/s if you don't actually use agents in parallel. Benchmark : RTX5090, Qwen3.6 35B loaded via LM studio with parallel tasks set to 8
Benchmark shows that running 4-5 parallel agents with LM Studio on RTX 5090 maximizes throughput, while more agents yield diminishing returns due to VRAM and compute splitting.
@dangerm00se: The main thing I had fable doing was routing moa and rlm experiments spanning local api and cerebras. Get your agent to…
The author shares findings from Hermes Mixture-of-Agents experiments, including voter upgrades, GPU topology, and caching economics, showing that local prefix caching can make long agent sessions nearly free and that two independent GPU instances outperform a single partitioned one.
We stopped sending every AI agent request to Claude Opus 5. The results surprised us.
A team benchmarked routing different stages of an AI agent workflow to different models versus sending every request to Claude Opus 5 across 89 Terminal-Bench 2.1 tasks, and found surprising results.