driver/framework news roundup

[dockriver]

Spent some time on this today and wanted to compare notes.

I'm comparing two approaches here: keep it simple on 5090, or squeeze more out of the stack and deal with the complexity.

Trying to avoid rebuilding the whole thing twice.

My use case is pretty ordinary: local chat, some document work, and occasional batch jobs.

[fastlab]

Maybe, but I had the opposite result. The reported numbers can look compelling, but in ordinary usage I didn't see the same benefit. Not saying you're wrong, just that I wouldn't lock that in as the lesson yet.

[routearch]

That matches what I was seeing. That matches what I saw on M3 Max. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable.

[cacheline]

Thanks, that helps. I don't think your conclusion is far off. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable.

[thetaember38]

What worked for me was pretty simple. If you're on LM Studio, I'd confirm the version first and then reduce variables until the behavior is obvious.

[northgarden37]

worth checking the driver first.

[papermixer4]

I'd approach it in a boring order. Before rebuilding anything, I'd test one clean baseline with Gemma and compare from there.

[batchember]

worth checking the driver first.

[dockriver]

Good point. That matches what I saw on dual 3090. The biggest change for me was simplifying the stack instead of adding one more optimization layer.