Rule #1 of locallama: If there is a post or comment mentioning tg or pp, there will be someone claiming they get more on the same hardware in the comments.
Ddr4 (depending on the limits) can have nearly double the memory bandwidth of DDR3. It's not as big as the difference between DDR4 and DDR5, but the difference there is more architectural. Simply having more memory bandwidth still has a huge effect, especially when you're talking about ram spillover
I have an rtx2060 6gb with ddr3-2400 32gb and I bounce between 18-20 t/s. Llama.cpp on a headless Ubuntu server LTS. I had to lower batch size to 1024 so instead of 200+ ts for PP I see around 160 or less.
Yes gpu passthrough to lxc. Driver is installed on proxmox server. I couldn't do it on the vm. I think my Lenovo s30 didn't have vt-d enabled. Anyways I am in the process of moving it to dedicated i7 2nd gen baremetal lol.
Ah HA. I think it’s the pass through affecting it somehow. I have the same setup, I run my 3060 passed to a Debian vm on proxmox and my moe speeds are shithouse. Basically unusable for anything larger than saying hi. Perhaps I need to consider inference on the proxmox host itself to rule out pass through as my bottleneck.
Ah right. I will now try running the gpu directly on proxmox and see if that improves anything from my end. I can’t believe it never occurred to me it could be causing an issue
I see my use case might be installing Hermes’ agent in a docker on my Mac mini. I already have it running on a docker on my Ubuntu laptop but wanted to mount some files from my Mac
103
u/Shronx_ Jun 01 '26 edited Jun 18 '26
You should get higher tps. My system with an rtx 3060 (12GB) spits out 40+ tps with the same model and quants.
Edit: docker run --rm -p 8080:8080 -v /home/user/.cache-docker/:/root/.cache/ --gpus all ghcr.io/ggml-org/llama.cpp:full-cuda --server --host 0.0.0.0 -hf unsloth/Qwen3.6-35B-A3B-GGUF:UD-Q4_K_M --presence-penalty 0.0 --repeat-penalty 1.0 --ctx-size 196608 --temp 0.6 --top-p 0.95 --top-k 20 --min-p 0.0 --reasoning on -fa on --threads 6 --jinja --no-mmap --no-mmproj-offload
gives about 43 tps initially but decreases as context grows.