+- Inference (https://www.datasculpting.ai/inference)
+-- Forum: Prompting & Context Engineering (https://www.datasculpting.ai/inference/forumdisplay.php?fid=15)
+--- Forum: Long Context / Memory (https://www.datasculpting.ai/inference/forumdisplay.php?fid=64)
+--- Thread: long context that stayed useful for Llama (/showthread.php?tid=326)
Pages:
1
2
long context that stayed useful for Llama - emberquill - 09-17-2026
Curious what people here are seeing.
I'm trying to decide whether to keep the current stack or change course. Main question is how people here are handling tail latency.
Would appreciate practical advice rather than theory.
Re: long context that stayed useful for Llama - syshouse - 09-18-2026
My first guess would be this: On B200, the easiest win is often to back off the aggressive settings and see whether the problem survives.
Re: long context that stayed useful for Llama - sanescope - 09-18-2026
Quote:My first guess would be this: On B200, the easiest win is often to back off the aggressive settings and see whether the problem survives.
Good point. I ended up in about the same place using Ollama. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable.
Re: long context that stayed useful for Llama - bytesupply76 - 09-18-2026
I tested this tonight. On 5090 with MLX, I saw basically the same behavior. The surprise was that memory pressure showed up before throughput collapsed.
Re: long context that stayed useful for Llama - torchkite - 09-19-2026
A couple things I'd check first. Before rebuilding anything, I'd test one clean baseline with Mistral and compare from there. Once you know the plain path works, then add the faster path back in piece by piece.
Re: long context that stayed useful for Llama - cozywire - 09-19-2026
Thanks, that helps. That matches what I saw on B200.
Re: long context that stayed useful for Llama - quantyard - 09-22-2026
My first guess would be this: If you're on SGLang, I'd confirm the version first and then reduce variables until the behavior is obvious. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.
Re: long context that stayed useful for Llama - quiethouse - 09-23-2026
A couple things I'd check first. On mini PC, the easiest win is often to back off the aggressive settings and see whether the problem survives. Not glamorous advice, but repeatable baselines save a lot of time.
Re: long context that stayed useful for Llama - audiopoint18 - 09-23-2026
Maybe, but I had the opposite result. I get why that seems right, but on dual 3090 the bottleneck felt elsewhere. Could be a workload difference, but I wouldn't generalize too fast from one setup.
Re: long context that stayed useful for Llama - tinycontext - 09-23-2026
following this because I'm in the same boat.
There are a few different conversations hiding inside this thread, so being explicit about the goal helps.