Can the RTX 4060 run WeVisCut?
WeVisCut·9.4B·GeForce RTX 4060·8 GB VRAM
Yes. The RTX 4060 runs WeVisCut fully in VRAM at Q4_K_M (about 7.0 GB of 8.0 GB), at roughly 26 tokens/s.
- best quant
- Q4_K_M
- needs
- 7.0 GB
- usable
- 8.0 GB
- est. speed
- ~26 tok/s
Estimates for an 8K context; offload assumes 32 GB of system RAM.Try other contexts on the WeVisCut page →
Every quantisation of WeVisCut on the RTX 4060
| Quant | Memory | Fit | Speed |
|---|---|---|---|
| Q2_K | 4.5 GB | fits | ~48 tok/s |
| Q3_K_M | 6.0 GB | fits | ~33 tok/s |
| Q4_K_M pick | 7.0 GB | fits | ~26 tok/s |
| Q5_K_M | 7.8 GB | tight | ~22 tok/s |
| Q6_K | 8.7 GB | offload | ~15 tok/s |
| Q8_0 | 11 GB | offload | ~7.8 tok/s |
| FP16 / BF16 | 19 GB | offload | ~2.6 tok/s |
Speed is a bandwidth-based estimate for generating text (272 GB/s); prompt processing and long contexts are slower.
Measured speed on the RTX 4060
No community reports for this pair yet.
Report your own speed →Run WeVisCut on the RTX 4060
Using Q4_K_M, the best fit for RTX 4060.
llama-server -hf prithivMLmods/tencent-WeVisCut-GGUF:Q4_K_MDownloads the GGUF on first run. Installed through llama.app? The same flags work with `llama serve`.
vllm serve tencent/WeVisCutservices:
vllm:
image: vllm/vllm-openai:latest
command: tencent/WeVisCut
ports:
- "8000:8000"
ipc: host
volumes:
- ~/.cache/huggingface:/root/.cache/huggingface
deploy:
resources:
reservations:
devices:
- driver: nvidia
count: all
capabilities: [gpu]API on port 8000.
sglang serve tencent/WeVisCut --host 0.0.0.0 --port 30000services:
sglang:
image: lmsysorg/sglang:latest
command: sglang serve tencent/WeVisCut --host 0.0.0.0 --port 30000
ports:
- "30000:30000"
ipc: host
volumes:
- ~/.cache/huggingface:/root/.cache/huggingface
deploy:
resources:
reservations:
devices:
- driver: nvidia
count: all
capabilities: [gpu]API on port 30000.
Omni models that fit the RTX 4060 comfortably
All that fit →| Model | Params | Best quant | Memory | Speed |
|---|---|---|---|---|
| 9.4B | Q5_K_M | ≈7.3 GBFits in memory | ~22 tok/s | |
| 8B | Q5_K_M | ≈6.5 GBFits in memory | ~26 tok/s | |
| 10.7B | Q6_K | ≈7.0 GBFits in memory | ~17 tok/s | |
| 9.1B | Q4_K_M | ≈7.0 GBFits in memory | ~27 tok/s | |
| 8.3B | Q6_K | ≈7.6 GBFits in memory | ~22 tok/s | |
| 8.7B | Q6_K | ≈7.0 GBFits in memory | ~21 tok/s |
Other GPUs that run WeVisCut
Frequently asked questions
- Can the RTX 4060 run WeVisCut?
- Yes. The RTX 4060 runs WeVisCut fully in VRAM at Q4_K_M (about 7.0 GB of 8.0 GB), at roughly 26 tokens/s.
- How fast does WeVisCut run on the RTX 4060?
- An estimate from memory bandwidth gives about 26 tokens/s at Q4_K_M.
- Which quantisation of WeVisCut should I use on the RTX 4060?
- Q4_K_M: the largest one that fits. Expected quality: small loss compared with the full-precision weights.
Memory and speed are estimates from the model's size and the card's memory bandwidth; real numbers depend on the runtime, drivers and context length. Community figures are medians of user reports.