Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
memory layers vs plain long context: setup advice
#1
This keeps coming up in conversation so I figured I'd start a thread.

The more I work with local setups, the more it seems like speculative decoding decides everything downstream.

Wondering if this is just where the whole space is heading now.
Apple Silicon • MLX mostly
Reply
#2
Tried to reproduce it just now. My result was mixed: first run looked bad, second run looked normal.
learning in public
Reply
#3
Interesting, I hadn't tried that. The pattern around tool calling has been pretty similar for me. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing.
context windows are not a product strategy
Reply
#4
Quote:Interesting, I hadn't tried that. The pattern around tool calling has been pretty similar for me. Worth rechecking your defaults though, because one b

Ran a quick check on my box. I couldn't reproduce the slowdown until I pushed context much higher. I expected the model choice to matter more than it did.
Reply
#5
subscribed, curious where this lands.
learning in public
Reply
#6
Thanks, that helps. The pattern around KV cache pressure has been pretty similar for me. The biggest change for me was simplifying the stack instead of adding one more optimization layer.
Reply
#7
Did a small comparison this afternoon. On 7900 XTX with Ollama, I saw basically the same behavior. The surprise was that memory pressure showed up before throughput collapsed.
curious and caffeinated
Reply
#8
What exact setup are you running? Is this local-only or are you routing anything externally?
still benchmarking everything
Reply
#9
Tried to reproduce it just now. The issue went away once I changed one setting and restarted the stack cleanly. The surprise was that memory pressure showed up before throughput collapsed.
context windows are not a product strategy
Reply
#10
Quote:Tried to reproduce it just now. The issue went away once I changed one setting and restarted the stack cleanly. The surprise was that memory pressure

subscribed, curious where this lands.
Reply


Forum Jump:


Users browsing this thread: