Can I run DeepSeek-Coder-V2-Lite-Base on a GeForce RTX 3050?

Yes. The best fit is I1-IQ1_S at 8,192 context with q4_0 KV — 5.53 GiB of 5.58 GiB usable, leaving 0.05 GiB headroom. Expect roughly 87 tokens/sec (modeled, ±37%).

From the file· weights summed from filesFrom the file· KV computed per layerPredicted· speed and compute buffer
KV cache dtypef16q8_0q4_06 GB card, 5.58 GiB usable after overhead

Every quantization at every context

total memory required; green fits, red does not
QuantWeights4K8K16K32K64K128K
BF1629.27 GiB30.130.130.230.330.631.1
Q8_015.56 GiB16.416.416.516.616.917.4
I1-Q6_K13.10 GiB13.914.014.014.214.415.0
Q6_K13.10 GiB13.914.014.014.214.415.0
I1-Q5_K_M11.04 GiB11.911.912.012.112.412.9
Q5_K11.04 GiB11.911.912.012.112.412.9
I1-Q5_K_S10.38 GiB11.211.311.311.511.712.3
Q5_K_S10.38 GiB11.211.311.311.511.712.3
I1-Q4_K_M9.65 GiB10.510.510.610.711.011.5
Q4_K9.65 GiB10.510.510.610.711.011.5
Q4_K_M9.65 GiB10.510.510.610.711.011.5
I1-Q4_K_S8.88 GiB9.79.89.810.010.210.8
Q4_K_S8.88 GiB9.79.89.810.010.210.8
I1-Q4_08.32 GiB9.29.29.39.49.710.2
IQ4_NL8.29 GiB9.19.29.29.49.610.2
I1-IQ4_XS7.98 GiB8.88.98.99.19.39.9
IQ4_XS7.98 GiB8.88.98.99.19.39.9
I1-Q3_K_L7.88 GiB8.78.88.89.09.29.8
Q3_K_L7.88 GiB8.78.88.89.09.29.8
I1-Q3_K_M7.57 GiB8.48.48.58.68.99.4
Q3_K7.57 GiB8.48.48.58.68.99.4
I1-IQ3_M7.03 GiB7.97.98.08.18.48.9
IQ3_M7.03 GiB7.97.98.08.18.48.9
I1-IQ3_S6.97 GiB7.87.97.98.18.38.9
I1-Q3_K_S6.97 GiB7.87.97.98.18.38.9
IQ3_S6.97 GiB7.87.97.98.18.38.9
Q3_K_S6.97 GiB7.87.97.98.18.38.9
I1-IQ3_XS6.63 GiB7.57.57.67.78.08.5
IQ3_XS6.63 GiB7.57.57.67.78.08.5
I1-IQ3_XXS6.49 GiB7.37.47.47.67.88.4
IQ3_XXS6.49 GiB7.37.47.47.67.88.4
Q2_K_S6.01 GiB6.96.97.07.17.47.9
I1-Q2_K5.99 GiB6.86.96.97.17.37.9
Q2_K5.99 GiB6.86.96.97.17.37.9
I1-IQ2_M5.89 GiB6.76.86.87.07.27.8
IQ2_M5.89 GiB6.76.86.87.07.27.8
I1-IQ2_S5.59 GiB6.46.56.56.76.97.5
IQ2_S5.59 GiB6.46.56.56.76.97.5
I1-IQ2_XS5.56 GiB6.46.46.56.66.97.4
IQ2_XS5.56 GiB6.46.46.56.66.97.4
I1-IQ2_XXS5.25 GiB6.16.16.26.36.67.1
IQ2_XXS5.25 GiB6.16.16.26.36.67.1
I1-IQ1_M4.88 GiB5.75.85.86.06.26.8
IQ1_M4.88 GiB5.75.85.86.06.26.8
I1-IQ1_S4.65 GiB5.55.55.65.76.06.5
IQ1_S4.65 GiB5.55.55.65.76.06.5
From the filePredictedwhat these mean

Figures are GiB of total memory: weights plus KV cache plus compute buffer and backend overhead. Weights and KV are near-exact; the overhead term is modeled. Hover any cell for the breakdown.

Run it

The best-fitting configuration above, as a command:

llama-cli -hf deepseek-ai/DeepSeek-Coder-V2-Lite-Base \
  --ctx-size 8192 \
  --cache-type-k q4_0 --cache-type-v q4_0 \
  -ngl auto

Recent llama.cpp defaults to --fit on with -ngl auto, so it will size the offload for you. The question worth your attention is not how many layers to offload but what context and quantization you are willing to live with — which is what the grid above is for.

Why other calculators disagree

A parameters × bits ÷ 8 estimate ignores two things that dominate at long context. First, the weights themselves are not the nominal rate — quantizations are mixtures, so the real file is consistently larger than the label implies. Second, this model uses latent attention and allocates no V cache at all, so any formula reading num_key_value_heads overstates its cache by more than an order of magnitude.