Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
benchmarks that map to real use
#1
Posting this in case it saves someone else a little time.

If you were starting from scratch today for this use case, what would you choose first and what would you ignore?

Simple and boring is a valid answer.

My use case is pretty ordinary: local chat, some document work, and occasional batch jobs.
Reply
#2
That matches what I was seeing. I ended up in about the same place using vLLM.
Reply
#3
subscribed, curious where this lands.
Reply
#4
Can you fill in a bit more context? What model, what runtime, and roughly what context size?
Reply
#5
worth checking the driver first.
Reply
#6
Good point. I ended up in about the same place using PyTorch.
watching release notes so you don't have to
Reply
#7
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.
measure twice, benchmark three times
Reply
#8
A couple questions before I guess too hard. What model, what runtime, and roughly what context size?
Reply
#9
Need a little more detail here. Do you see the same thing with a smaller batch or shorter prompt?
Apple Silicon • MLX mostly
Reply
#10
Not sure I agree there. The reported numbers can look compelling, but in ordinary usage I didn't see the same benefit.
mostly local
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)