This keeps coming up in conversation so I figured I'd start a thread.

It feels like the conversation has shifted hard toward inference and serving details lately, and honestly that makes sense once you start dealing with KV cache pressure.

Wondering if this is just where the whole space is heading now.

I care more about stability than squeezing the last possible tokens/sec out of it.

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

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

Trying to avoid rebuilding the whole thing twice.

I care more about stability than squeezing the last possible tokens/sec out of it.

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?

I'm especially interested in mistakes worth avoiding.

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

Two paths both seem viable, but they break down differently once VRAM headroom becomes important.

What would you pick if you had to live with it for a few months?

Did a bit of testing and thought I'd post the result here.

After a few runs on A6000, I ended up with decent performance, but the setup only really made sense once I adjusted around workstation thermals.

Nothing scientific here, just practical notes from a real setup.

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

Did a bit of testing and thought I'd post the result here.

I tried this with Mixtral using SGLang on Threadripper box. The headline result was better than I expected, but HBM constraints still ended up being the limiting factor.

Curious if anyone else landed in the same place.

I care more about stability than squeezing the last possible tokens/sec out of it.

Thought I'd post a small recipe because a lot of threads ask similar things.

This isn't revolutionary, but the combination of Ollama and 4090 felt surprisingly usable once I tuned around embeddings.

Maybe useful as a starting point for newer folks.

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

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

Interested in tradeoffs more than fan loyalty.

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

Has anyone else run into this?

I'm trying to decide whether to keep the current stack or change course. Main question is how people here are handling KV cache pressure.

If you've tested something similar, what did you keep and what did you stop bothering with?

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

Two paths both seem viable, but they break down differently once batch size becomes important.

What would you pick if you had to live with it for a few months?

This is mostly for local work rather than public serving.