Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
RAG chunking that actually helped on Threadripper box
#11
I think the bottleneck is somewhere else. The reported numbers can look compelling, but in ordinary usage I didn't see the same benefit.
Reply
#12
That matches what I was seeing. I don't think your conclusion is far off. The biggest change for me was simplifying the stack instead of adding one more optimization layer.
Reply
#13
A couple things I'd check first. Before rebuilding anything, I'd test one clean baseline with Gemma and compare from there.
Reply
#14
A couple questions before I guess too hard. What model, what runtime, and roughly what context size?
Reply
#15
Not sure I agree there. I wouldn't optimize around that first. On my side the bigger swing came from the runtime and not the model. Not saying you're wrong, just that I wouldn't lock that in as the lesson yet. The logs were somehow calmer than I was.
Reply
#16
Ran a quick check on my box. My result was mixed: first run looked bad, second run looked normal. The surprise was that memory pressure showed up before throughput collapsed.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)