Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
small agent harness that stayed useful
#1
Did a bit of testing and thought I'd post the result here.

Short version: Ollama behaved well for me, but only after I stopped ignoring prefill/decode split.

Happy to post more details if anyone wants them.

For context, I'm not chasing leaderboard numbers. I mostly want the system to feel consistent day to day.
learning in public
Reply
#2
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.
Reply
#3
That matches what I was seeing. The pattern around small local stacks has been pretty similar for me. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable.
still benchmarking everything
Reply
#4
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.
still benchmarking everything
Reply
#5
A couple things I'd check first. If you're on Ollama, I'd confirm the version first and then reduce variables until the behavior is obvious. Not glamorous advice, but repeatable baselines save a lot of time.
LoRA tinkerer • dataset janitor
Reply
#6
That matches what I was seeing. That matches what I saw on mini PC.
Reply
#7
I don't think that's the whole story. 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.
still benchmarking everything
Reply
#8
A couple things I'd check first. If you're on llama.cpp, I'd confirm the version first and then reduce variables until the behavior is obvious. Not glamorous advice, but repeatable baselines save a lot of time.
LoRA tinkerer • dataset janitor
Reply
#9
Quote:A couple things I'd check first. If you're on llama.cpp, I'd confirm the version first and then reduce variables until the behavior is obvious. Not gl

Did a small comparison this afternoon. On mini PC with Ollama, I saw basically the same behavior. The main thing that moved was latency, not quality.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)