10-14-2026, 09:47 AM
I'd approach it in a boring order. Before rebuilding anything, I'd test one clean baseline with Mixtral and compare from there. Not glamorous advice, but repeatable baselines save a lot of time.
|
Apple unified memory limits: setup advice
|
|
10-14-2026, 09:47 AM
I'd approach it in a boring order. Before rebuilding anything, I'd test one clean baseline with Mixtral and compare from there. Not glamorous advice, but repeatable baselines save a lot of time.
10-14-2026, 10:32 AM
Quote:I'd approach it in a boring order. Before rebuilding anything, I'd test one clean baseline with Mixtral and compare from there. Not glamorous advice, Can you fill in a bit more context? Is this local-only or are you routing anything externally?
10-14-2026, 11:15 AM
Quote:[quote]I'd approach it in a boring order. Before rebuilding anything, I'd test one clean baseline with Mixtral and compare from there. Not glamorous a A couple things I'd check first. Before rebuilding anything, I'd test one clean baseline with Llama and compare from there. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.
learning in public
10-14-2026, 11:31 PM
A couple questions before I guess too hard. Are you testing this on GB200 or something else?
10-16-2026, 12:09 AM
That matches what I was seeing. The pattern around continuous batching 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.
10-16-2026, 12:27 AM
My first guess would be this: Before rebuilding anything, I'd test one clean baseline with Mistral and compare from there. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.
I'm happy to test one more variant if you want a second data point. |
|
« Next Oldest | Next Newest »
|