Posts: 43
Threads: 8
Joined: Sep 2026
Reputation:
0
This keeps coming up in conversation so I figured I'd start a thread.
One thing I keep noticing is that people underestimate prefill/decode split until they actually try to run this stuff for more than one afternoon.
Wondering if this is just where the whole space is heading now.
Posts: 85
Threads: 12
Joined: Aug 2026
Reputation:
0
I think the bottleneck is somewhere else. I've seen people blame consumer GPUs when the real issue was much more mundane. Could be a workload difference, but I wouldn't generalize too fast from one setup.
LoRA tinkerer • dataset janitor
Posts: 36
Threads: 7
Joined: Sep 2026
Reputation:
0
Can you fill in a bit more context? Do you see the same thing with a smaller batch or shorter prompt?
Posts: 45
Threads: 2
Joined: Aug 2026
Reputation:
0
I tested this tonight. My result was mixed: first run looked bad, second run looked normal.
Posts: 57
Threads: 9
Joined: Aug 2026
Reputation:
0
I'd start with the simpler stack.
Posts: 26
Threads: 4
Joined: Aug 2026
Reputation:
0
Not sure I agree there. I've seen people blame batch size when the real issue was much more mundane.
Posts: 25
Threads: 2
Joined: Sep 2026
Reputation:
0
subscribed, curious where this lands.
Posts: 59
Threads: 8
Joined: Sep 2026
Reputation:
0
A couple things I'd check first. On Threadripper box, the easiest win is often to back off the aggressive settings and see whether the problem survives. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.
Posts: 56
Threads: 7
Joined: Sep 2026
Reputation:
0
Good point. The pattern around token cost 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.