Replies: 2 comments 1 reply
|
Thanks for the full Your PCIe link is training at Gen1, not Gen3. From your own report (
This Gen1 down-train is a known Proxmox VFIO-passthrough behavior. Things to check, in order:
Once the link is at Gen3, two secondary items for the remaining gap — both are the lesson from #161 (NUMA-alignment + vCPU pinning moved that rig 20→60 tok/s):
On NVLink: your report shows it is bonded and engaged (NV4, ~14 GB/s/link), but (Minor: the report's "⚠ something is using this GPU — 23848 MiB" is a false positive here — that's just your
|
|
Thank you for your feedback :-) I have checked your suggestions and I discovered that:
I made a number of experiments and configuration (simplified) that works best for me now is below. Important changes:
Benchmark: URL=http://localhost:8010 CONTAINER=vllm-qwen36-27b-dual ./scripts/bench.sh && ./scripts/verify-stress.sh === measured (5) === === summary [narrative] (n=5) === ========== CODE (prompt=78 chars, max_tokens=800) ========== === measured (5) === === summary [code] (n=5) === === GPU state === === Last 3 SpecDecoding metrics === [1/7] Long-context needle small rungs (10K / 30K) ... All stress / boundary checks passed. KV-cache and prefill paths are sound for the deployed config. [soak] summary docker-compose.yml |
Uh oh!
There was an error while loading. Please reload this page.
Hi,
Can you please have a look into to my config and report results? Maybe you can help me to fill the gap between my inference performance and the one you are geting ...
Related to: Optimizing LLM inference performance with Dual RTX 3090 + NVLink on Proxmox
At the moment, after Proxmox VM configuration, I'm achieving around 41 tokens per second NARRATIVE and ~ 55 tokens pers second CODE. GPU power is capped to 260W (from 350W) but it makes near no difference in inference speed.
It is still much less than what docs mentions (69/89) but it is already usable as I started from ~ 20 tokens per second.
My hardware setup is
Dell T630 server
2X Intel(R) Xeon(R) CPU E5-2695 v4 @ 2.10GHz
256GB DDR4 RAM,
2x RTX3090 in PCIe 3.0 x 16
VLLM runs in Proxmox VM with GPU's being pass-through to VM
This is my report
~/club-3090$ bash scripts/report.sh --full
club-3090 rig report
Generated: 2026-05-18 14:48:51 UTC
Redacted output (paths, host, user, tokens). Re-run with
--no-redactfor full data.System
CPU + RAM
Disk
GPU hardware
NVLink
NVLink link status
Topology
PCIe / GPU topology matrix
PCIe / P2P detail (lspci)
lspci PCIe/P2P detail (LnkSta / ACS / topology)
Full nvidia-smi
Full nvidia-smi output
Display / desktop state
Container runtime
Stack version
v0.8.0-17-g135f2c4(branch:master, SHA135f2c4)7b9fd319(per scripts/setup.sh)nightly-bf610c2f56764e1b30bc6065f4ceace3d6e59036digestsha256:7f047b7e625283eee436cfc0c37784064f75422452ed4f9b6fa8c69eae6afe68(3 days ago)Profile state
~/.club3090/estate.ymlnot found)KV math calibration
Full kv-calc --calibration output
Active container
vllm-qwen36-27b-dualvllmvllm/vllm-openai:nightly-bf610c2f56764e1b30bc6065f4ceace3d6e59036Container Python / CUDA versions
torch=2.11.0+cu130 torch_cuda_build=13.0 cudnn=919000.20.2rc1.dev371+gbf610c2f5Boot log highlights
KV pool sizing:
Engine config (CLI flags + engine init):
Recent warnings/errors (last 5):
Full boot log (first 200 lines)
First 200 lines of docker logs
Recent failed boot attempts
No recently-exited vLLM or llama.cpp containers found.
verify-full.sh output
verify-full output
verify-stress.sh output
verify-stress output (7 boundary checks incl. Cliff 2 needle recall)
soak-test.sh (SOAK_MODE=continuous) output
soak-test stdout (5-session × 5-turn ramping conversation, ~25 min)
Soak summary (
results/report-soak-20260518-145326/summary.md):Soak test summary
Recommendation
bench.sh output
bench output (3 warmups + 5 measured per prompt)
Generated by
bash scripts/report.sh. Flags:--verify(verify-full),--stress(verify-stress 7/7 incl. Cliff 2 needles),--soak(SOAK_MODE=continuous, catches Cliff 2b),--bench(canonical TPS),--full(all four, ~35 min). Use--no-redactto disable redaction (internal sharing only).All reactions