Can Codestral 21B Pruned i1 run on RTX 4060 Ti 16GB?

BARELY — Tight on Memory

D36Poor
Estimated from fit model

Codestral 21B Pruned i1 needs ~18.1 GB VRAM. RTX 4060 Ti 16GB has 16.0 GB. With Q4_K_M quantization, expect ~10 tok/s.

Runtime: OllamaCapacity: OffloadBandwidth: LowStack: BasicBottleneck: Host offload
Share:

Operating mode

Choose the run profile you care about

Interactive favors responsiveness, while light API and scale-out lean harder on serving readiness. The fit stays the same, but the recommendation lens changes.

Current mode

Balanced

Balanced for general local use. Keeps the ranking neutral across personal and serving workflows.

Capabilities:

Select quantization to explore

Q4_K_M (Medium quality) 18.1 GB, 9.5 tok/s, Very compromised (needs ~1.5 GB host RAM)
18.1 GB required16.0 GB available
113% VRAM needed

2.1 GB over capacity — needs offload or smaller quantization

Fit status

Very compromised (needs ~1.5 GB host RAM)

Decode

9.5 tok/s

TTFT

20321 ms

Safe context

4K

Memory

18.1 GB / 16.0 GB

Offload

10%

Memory breakdown

Weights12.8 GB
KV Cache2.5 GB
Runtime1.2 GB
Headroom1.6 GB

See how fast it feels

See how fast it feelsCodestral 21B Pruned i1 on RTX 4060 Ti 16GB
1st promptCold start — includes initialization
>Write a Python function to sort a list
Here's a Python function that sorts a list using quicksort: def quicksort(arr): if len(arr) <= 1: return arr pivot = arr[len(arr) // 2] left = [x for x in arr if x < pivot] middle = [x for x in arr if x == pivot] right = [x for x in arr if x > pivot] return quicksort(left) + middle + quicksort(right) # Example usage numbers = [3, 6, 8, 10, 1, 2, 1] print(quicksort(numbers)) # [1, 1, 2, 3, 6, 8, 10] The algorithm picks a pivot, partitions the list into smaller, equal, and larger elements, then recursively sorts each partition and concatenates the results.
2nd promptWarm — model ready, no init overhead
>Now add type hints and a docstring
def quicksort(arr: list[int]) -> list[int]: """Sort a list using the quicksort algorithm. Args: arr: List of integers to sort. Returns: A new sorted list. """ if len(arr) <= 1: return arr pivot = arr[len(arr) // 2] left = [x for x in arr if x < pivot] middle = [x for x in arr if x == pivot] right = [x for x in arr if x > pivot] return quicksort(left) + middle + quicksort(right) Added type hints for the input and return type, plus a Google-style docstring.
Estimated: 9.5 tok/s decode · 20.3s TTFT (warm) · 24 tok/s prefill

What limits this setup

It fits through host-memory offload, and offload is the main reason performance drops.

CPU or host-memory offload is active

About 10% of the working set spills out of accelerator memory, which usually hurts latency and sustained decode throughput.

Very little memory headroom

You can run the model, but there is not much room left for longer context, bigger batches, extra apps, or future model updates.

Best improvement path

Remove offload with more accelerator memory

Prioritize a GPU or unified-memory tier that fits the whole model natively. Removing offload usually helps more than small compute gains.

Buy headroom, not only minimum fit

A slightly larger memory tier gives you safer context growth and makes the recommendation more future-proof.

Increase host RAM if you keep offloading

This setup may need roughly 1.5 GB of extra host RAM just for the offloaded portion, before OS and other tools.

Performance by workload

WorkloadGradeFitDecodeTTFTContext
ChatCRuns with offload (needs ~0.6 GB host RAM)11.1 tok/s9555 ms4K
CodingDVery compromised (needs ~1.5 GB host RAM)9.5 tok/s20321 ms4K
Agentic CodingFToo heavy7.3 tok/s38672 ms4K
ReasoningDVery compromised (needs ~1.5 GB host RAM)9.5 tok/s24016 ms4K
RAGFToo heavy7.3 tok/s48340 ms4K

Quantization options

How Codestral 21B Pruned i1 (21B params) fits at each quantization level on RTX 4060 Ti 16GB (16.0 GB usable).

QuantBitsVRAMQualityFit
Q2_K
2
8.2 GB
LowC51
Q3_K_S
3
10.3 GB
LowC50
NVFP4Best for your GPU
4
11.8 GB
MediumC50
Q4_K_M
4
12.8 GB
MediumF0
Q5_K_M
5
15.1 GB
HighF0
Q6_K
6
17.2 GB
HighF0
Q8_0
8
22.5 GB
Very HighF0
F16
16
43.1 GB
MaximumF0

Get started

Copy-paste commands to run Codestral 21B Pruned i1 on your machine.

Run

lms load hf-mradermacher--codestral-21b-pruned-i1-gguf && lms server start

Upgrade-Optionen

Hardware, die Codestral 21B Pruned i1 gut ausführt

Frequently asked questions

Can RTX 4060 Ti 16GB run Codestral 21B Pruned i1?

Yes, RTX 4060 Ti 16GB can run Codestral 21B Pruned i1 with a D grade (Very compromised (needs ~1.5 GB host RAM)). Expected decode speed: 9.5 tok/s.

How much VRAM does Codestral 21B Pruned i1 need?

Codestral 21B Pruned i1 (21B parameters) requires approximately 18.1 GB of memory with Q4_K_M quantization.

What is the best quantization for Codestral 21B Pruned i1?

The recommended quantization for Codestral 21B Pruned i1 is Q4_K_M, which balances quality and memory efficiency.

What speed will Codestral 21B Pruned i1 run at on RTX 4060 Ti 16GB?

On RTX 4060 Ti 16GB, Codestral 21B Pruned i1 achieves approximately 9.5 tokens per second decode speed with a time-to-first-token of 20321ms using Q4_K_M quantization.

Can RTX 4060 Ti 16GB run Codestral 21B Pruned i1 for coding?

For coding workloads, Codestral 21B Pruned i1 on RTX 4060 Ti 16GB receives a D grade with 9.5 tok/s and 4K context.

What context window can Codestral 21B Pruned i1 use on RTX 4060 Ti 16GB?

On RTX 4060 Ti 16GB, Codestral 21B Pruned i1 can safely use up to 4K tokens of context. The model's official context limit is —, but available memory constrains the safe maximum.

What should I upgrade first if Codestral 21B Pruned i1 feels slow on RTX 4060 Ti 16GB?

Remove offload with more accelerator memory. Prioritize a GPU or unified-memory tier that fits the whole model natively. Removing offload usually helps more than small compute gains.

See all results for RTX 4060 Ti 16GBSee all hardware for Codestral 21B Pruned i1
Embed this result

Paste this snippet into any page to show a live fit card.

<iframe src="https://willitrunai.com/embed/hf-mradermacher--codestral-21b-pruned-i1-gguf-on-rtx-4060-ti-16gb" width="400" height="180" frameborder="0" style="border:none;border-radius:12px;overflow:hidden;" title="Will It Run AI — fit result"></iframe>

Preview: