| Welcome, Guest |
You have to register before you can post on our site.
|
| Online Users |
There are currently 122 online users. » 0 Member(s) | 121 Guest(s) Google
|
|
|
| consumer GPU serving economics on 4090 |
|
Posted by: relaynest82 - 08-27-2026, 08:49 AM - Forum: Performance Tuning
- Replies (11)
|
 |
Did a bit of testing and thought I'd post the result here.
After a few runs on Threadripper box, I ended up with decent performance, but the setup only really made sense once I adjusted around batch size.
Curious if anyone else landed in the same place.
My use case is pretty ordinary: local chat, some document work, and occasional batch jobs.
|
|
|
| AWQ vs GPTQ vs GGUF right now |
|
Posted by: cachelab - 08-27-2026, 05:56 AM - Forum: Quantization
- Replies (9)
|
 |
This keeps coming up in conversation so I figured I'd start a thread.
One thing I keep noticing is that people underestimate batch size until they actually try to run this stuff for more than one afternoon.
Maybe obvious to some of you, but it clicked for me this week.
|
|
|
| distill or just quantize for DeepSeek |
|
Posted by: turboyard94 - 08-27-2026, 03:17 AM - Forum: Agents
- Replies (12)
|
 |
Did a bit of testing and thought I'd post the result here.
I tried this with Phi using PyTorch on GB200. The headline result was better than I expected, but small local stacks still ended up being the limiting factor.
Nothing scientific here, just practical notes from a real setup.
This is mostly for local work rather than public serving.
|
|
|
| RAG chunking that actually helped for Llama |
|
Posted by: dockkite69 - 08-26-2026, 10:55 PM - Forum: Distillation
- Replies (2)
|
 |
Spent some time on this today and wanted to compare notes.
I've gone back and forth between TensorRT-LLM and llama.cpp for Qwen. The interesting difference for me has been speculative decoding.
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.
|
|
|
| setup notes worth sharing on 4090 |
|
Posted by: phasespark - 08-26-2026, 09:39 PM - Forum: Local
- Replies (1)
|
 |
Spent some time on this today and wanted to compare notes.
I'm comparing two approaches here: keep it simple on GB200, 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.
|
|
|
| quant support gaps on GB200 |
|
Posted by: routecrate - 08-26-2026, 08:31 PM - Forum: TensorRT-LLM
- Replies (14)
|
 |
This keeps coming up in conversation so I figured I'd start a thread.
The more I work with local setups, the more it seems like HBM constraints decides everything downstream.
Maybe obvious to some of you, but it clicked for me this week.
|
|
|
| CUDA update broke my throughput with TensorRT-LLM |
|
Posted by: audiopath66 - 08-26-2026, 07:31 PM - Forum: NVIDIA / CUDA
- Replies (11)
|
 |
I figured I'd ask here before changing everything.
I'm trying to decide whether to keep the current stack or change course. Main question is how people here are handling continuous batching.
If you've tested something similar, what did you keep and what did you stop bothering with?
For context, I'm not chasing leaderboard numbers. I mostly want the system to feel consistent day to day.
|
|
|
| prefix caching on repeated workflows |
|
Posted by: cacheline - 08-26-2026, 03:23 PM - Forum: Context / KV Cache
- No Replies
|
 |
Thought I'd post a small recipe because a lot of threads ask similar things.
Maybe useful as a starting point: vLLM on dual 3090, keeping INT4 in mind from the start.
Feel free to tear it apart if you see something dumb.
My use case is pretty ordinary: local chat, some document work, and occasional batch jobs.
|
|
|
|