| ▲ | cyanydeez 8 hours ago | |||||||||||||
I use exactly the setup you describe; it can handle 1-3 agents working if the agent work has IO delays. with MTP models, prefill is quite fast. Not sure what damage you have, but no one waits 40 minutes per prompt or even a minute; The A3B model loads within 10 seconds and a simple response in opencode is maybe at most a minute, then catches up in 3-5second bursts depending on IO. I put dynamic context pruning into opencode and tweaked it for 45k-85k context before it shrinks; this lets me get into 500k token sizes and fixed on medium sized github repos. There's a chance this comment is a skill error: 1. USe llamacpp with a MTP model 2. Use reasoning-budget and reasoning-message 3. Tailor your agent to use the reasoning-message to use subagents and dyanmic compaction. --- Now you have a reasonable coding agent for cloning, building and extending any github project I've seen so far. | ||||||||||||||
| ▲ | preya2k 8 hours ago | parent [-] | |||||||||||||
Are you on Strix Halo? If so, which llama.cpp backend are you using? ROCm on Strix Halo still seems incompatible with MTP models. | ||||||||||||||
| ||||||||||||||