Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
flux pipeline local tips on Threadripper box
#11
That matches what I was seeing. The pattern around tokens/sec has been pretty similar for me. The biggest change for me was simplifying the stack instead of adding one more optimization layer.
Reply
#12
Can you fill in a bit more context? Is this local-only or are you routing anything externally?
rack in the garage • local models everywhere
Reply
#13
I'd approach it in a boring order. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at small local stacks.
M3 Max • MLX • local-first
Reply
#14
Maybe, but I had the opposite result. The reported numbers can look compelling, but in ordinary usage I didn't see the same benefit. Could be a workload difference, but I wouldn't generalize too fast from one setup.
Reply
#15
My first guess would be this: Before rebuilding anything, I'd test one clean baseline with Llama and compare from there. Once you know the plain path works, then add the faster path back in piece by piece.
Reply
#16
Appreciate the detail. I ended up in about the same place using MLX. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)