Can Phi-3.5-mini-instruct run on GeForce RTX 4060 8GB (desktop)?
Conditional memory judgement for one configuration. Change context, quant, or engine and the conclusion can change.
Small dense model on 8GB, including long-context KV pressure.
Configuration used on this page: bf16, 8,192 cached tokens, 1 sequence, engine vllm.
Status: Insufficient memory. Software: Documented support.
Weights 7.12 GiB · raw KV 3.00 GiB · total 10.74 GiB–12.71 GiB.
Available budget 7.00 GiB after the default reserve.
This page is an estimate unless a matching runtime-resident measurement is attached.
- Full-resident weight estimates use total parameters, including inactive MoE experts.
- Weight bytes come from the selected weight files only, not from every file in the repository.
- Download file size is not peak GPU memory. Runtime layout, allocator padding, and KV are extra.
- Counted files: model.safetensors.index.json metadata.total_size.
- Context budget is the number of cached tokens per sequence (prompt plus reserved generation).
- Concurrent sequences share one model replica; weights are not multiplied by sequence count.
- KV dtype is independent of weight quantization unless you change it.
- Prefill peak and steady decode occupancy are not the same. The high scenario is closer to prefill/workspace pressure.
Related: Phi-3.5-mini-instruct· GeForce RTX 4060 8GB (desktop)
Estimate
Insufficient memory
Even the low estimate exceeds the available budget for this configuration.
Estimated memory range: 10.74 GiB – 12.71 GiB
Weights use selected file metadata. Runtime extras are still estimated.
Available budget: 7.00 GiB · Remaining after estimate: -5.71 GiB – -3.74 GiB
Software compatibility
Documented support. Enough memory does not mean this engine, quant, and OS will run. Support does not mean it will be fast.
Assumptions that affect this result
- Full-resident weight estimates use total parameters, including inactive MoE experts.
- Weight bytes come from the selected weight files only, not from every file in the repository.
- Download file size is not peak GPU memory. Runtime layout, allocator padding, and KV are extra.
- Counted files: model.safetensors.index.json metadata.total_size.
- Context budget is the number of cached tokens per sequence (prompt plus reserved generation).
- Concurrent sequences share one model replica; weights are not multiplied by sequence count.
- KV dtype is independent of weight quantization unless you change it.
- Prefill peak and steady decode occupancy are not the same. The high scenario is closer to prefill/workspace pressure.
- Engine reserve is not the same as bytes the model actually uses for weights and KV.
- vLLM often preallocates KV from remaining GPU memory. This estimate reports needed KV plus CUDA/graph extras, not the allocator leftover grab.
- PagedAttention block alignment can add a small amount above the raw KV payload.
- Host RAM is not added to discrete GPU VRAM.