Posts: 61
Threads: 6
Joined: Sep 2026
Reputation:
0
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.
Posts: 51
Threads: 4
Joined: Sep 2026
Reputation:
0
That matches what I was seeing. I ended up in about the same place using vLLM.
Posts: 41
Threads: 6
Joined: Oct 2026
Reputation:
0
subscribed, curious where this lands.
Posts: 65
Threads: 5
Joined: Sep 2026
Reputation:
0
Can you fill in a bit more context? What model, what runtime, and roughly what context size?
Posts: 44
Threads: 3
Joined: Oct 2026
Reputation:
0
worth checking the driver first.
Posts: 134
Threads: 18
Joined: Sep 2026
Reputation:
0
Good point. I ended up in about the same place using PyTorch.
watching release notes so you don't have to
Posts: 341
Threads: 51
Joined: Sep 2026
Reputation:
0
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
Posts: 25
Threads: 4
Joined: Sep 2026
Reputation:
0
A couple questions before I guess too hard. What model, what runtime, and roughly what context size?
Posts: 40
Threads: 3
Joined: Sep 2026
Reputation:
0
Need a little more detail here. Do you see the same thing with a smaller batch or shorter prompt?
Apple Silicon • MLX mostly
Posts: 39
Threads: 8
Joined: Aug 2026
Reputation:
0
Not sure I agree there. The reported numbers can look compelling, but in ordinary usage I didn't see the same benefit.
mostly local