![]() |
|
routing between local and hosted for Gemma - Printable Version +- Inference (https://www.datasculpting.ai/inference) +-- Forum: LLM Models (https://www.datasculpting.ai/inference/forumdisplay.php?fid=12) +--- Forum: Open Weight (https://www.datasculpting.ai/inference/forumdisplay.php?fid=49) +---- Forum: Recipes & Configurations (https://www.datasculpting.ai/inference/forumdisplay.php?fid=52) +---- Thread: routing between local and hosted for Gemma (/showthread.php?tid=1033) Pages:
1
2
|
Re: routing between local and hosted for Gemma - routecraft - 10-18-2026 My first guess would be this: On M3 Max, the easiest win is often to back off the aggressive settings and see whether the problem survives. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it. Re: routing between local and hosted for Gemma - dockkite69 - 10-18-2026 I tested this tonight. I couldn't reproduce the slowdown until I pushed context much higher. The main thing that moved was latency, not quality. Re: routing between local and hosted for Gemma - dockbrook21 - 10-19-2026 Maybe, but I had the opposite result. I get why that seems right, but on Threadripper box the bottleneck felt elsewhere. Not saying you're wrong, just that I wouldn't lock that in as the lesson yet. |