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.

Interested in tradeoffs more than fan loyalty.

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

I tried this with Gemma using TensorRT-LLM on 7900 XTX. 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.

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?

Would rather learn from your scars than collect my own all at once.

Maybe I'm missing something obvious.

My current setup is SGLang with Threadripper box, and I keep running into KV cache pressure.

Not looking for the perfect answer, mostly what worked in real use.

Posting this in case it saves someone else a little time.

I'm not trying to build a perfect architecture diagram. I just want a sane starting point around Ollama and A6000.

Would rather learn from your scars than collect my own all at once.

If I had to summarize the lesson so far, it would be that clean setup and observability beat clever guesses.

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

Two paths both seem viable, but they break down differently once KV cache pressure becomes important.

Interested in tradeoffs more than fan loyalty.

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

Just sharing a setup that ended up working reasonably well: Mixtral, llama.cpp, dual 3090, with a lot of attention on continuous batching.

Feel free to tear it apart if you see something dumb.

This is mostly for local work rather than public serving.

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

I've gone back and forth between vLLM and TensorRT-LLM for Phi. The interesting difference for me has been consumer GPUs.

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

For context, I'm not chasing leaderboard numbers. I mostly want the system to feel consistent day to day.

Maybe I'm missing something obvious.

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

Not looking for the perfect answer, mostly what worked in real use.

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

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

One thing I keep noticing is that people underestimate continuous batching until they actually try to run this stuff for more than one afternoon.

Curious whether that lines up with what other people are seeing.