Can Codestral 2 25.08 run on GTX 1080 Ti 11GB?

Q: What should I upgrade first if Codestral 2 25.08 feels slow on GTX 1080 Ti 11GB?

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.

YES — With Q2_K

B66Good

Estimated from fit model

Codestral 2 25.08 needs ~13.0 GB VRAM. GTX 1080 Ti 11GB has 11.0 GB. With Q2_K quantization, expect ~14 tok/s.

Runtime: llama.cppCapacity: OffloadBandwidth: MediumStack: StandardBottleneck: Host offload

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.

Codestral 2 25.08 at Q4_K_M needs 17.9 GB — too much for GTX 1080 Ti 11GB (11.0 GB). Runs at Q2_K (13.0 GB) with low quality.

Capabilities:

Select quantization to explore

Q4_K_M (Medium quality) — 17.9 GB, exceeds 11.0 GB available

17.9 GB required11.0 GB available

163% VRAM needed

6.9 GB over capacity — needs offload or smaller quantization

Fit status

Too heavy

Decode

5.1 tok/s

TTFT

37674 ms

Safe context

Memory

17.9 GB / 11.0 GB

Offload

40%

Memory breakdown

Weights13.4 GB

KV Cache2.4 GB

Runtime0.9 GB

Headroom1.1 GB

See how fast it feels

With memory offload — actual speed may be lower

See how fast it feelsCodestral 2 25.08 on GTX 1080 Ti 11GB
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: 5.1 tok/s decode · 37.7s TTFT (warm) · 13 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 20% 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.

Older PCIe generation

PCIe 3.0 is workable, but it compounds the penalty when you offload heavily or try to scale across multiple cards.

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.3 GB of extra host RAM just for the offloaded portion, before OS and other tools.

Performance by workload

Workload	Grade	Fit	Decode	TTFT	Context
Chat	F	Too heavy	6.0 tok/s	17591 ms	4K
Coding	F	Too heavy	4.8 tok/s	40499 ms	4K
Agentic Coding	F	Too heavy	3.9 tok/s	72602 ms	4K
Reasoning	F	Too heavy	5.1 tok/s	44523 ms	4K
RAG	F	Too heavy	3.9 tok/s	90753 ms	4K

Quantization options

How Codestral 2 25.08 (22B params) fits at each quantization level on GTX 1080 Ti 11GB (11.0 GB usable).

Quant	Bits	VRAM	Quality	Fit
Q2_K	2	8.6 GB	Low	F0
Q3_K_S	3	10.8 GB	Low	F0
NVFP4	4

Get started

Copy-paste commands to run Codestral 2 25.08 on your machine.

Run

lms load codestral-2508 && lms server start

Upgrade options

Hardware that runs Codestral 2 25.08 well

RTX 5060 Ti 16GBBest value

16 GB VRAM (+5)

Makes the model fit on the accelerator instead of staying completely out of reach.9.1 tok/s decode

Makes the model fit on the accelerator instead of staying completely out of reach.

Raises estimated decode speed by about 78%.

~$449 MSRP

RTX 4060 Ti 16GBNVIDIA upgrade

16 GB VRAM (+5)

Makes the model fit on the accelerator instead of staying completely out of reach.6.4 tok/s decode

Makes the model fit on the accelerator instead of staying completely out of reach.

Raises estimated decode speed by about 25%.

~$499 MSRP

RTX 4000 Ada 20GBBudget pick

20 GB VRAM (+9)

Makes the model fit on the accelerator instead of staying completely out of reach.20.1 tok/s decode

Makes the model fit on the accelerator instead of staying completely out of reach.

Removes host-memory offload, which is usually the single biggest latency and throughput win.

~$1,250 MSRP

RTX 5090 Laptop 24GBBiggest leap

24 GB VRAM (+13)896 GB/s (+412)

Makes the model fit on the accelerator instead of staying completely out of reach.53.8 tok/s decode

Makes the model fit on the accelerator instead of staying completely out of reach.

Removes host-memory offload, which is usually the single biggest latency and throughput win.

Frequently asked questions

Can GTX 1080 Ti 11GB run Codestral 2 25.08?

Yes, GTX 1080 Ti 11GB can run Codestral 2 25.08 at Q2_K quantization (Very compromised (needs ~1.3 GB host RAM)). The recommended Q4_K_M requires 17.9 GB which exceeds available memory, but at Q2_K it needs only 13.0 GB. Expected decode speed: 13.7 tok/s.

How much VRAM does Codestral 2 25.08 need?

Codestral 2 25.08 (22B parameters) requires approximately 17.9 GB at Q4_K_M quantization. On GTX 1080 Ti 11GB, it fits at Q2_K using 13.0 GB.

What is the best quantization for Codestral 2 25.08?

The recommended quantization is Q4_K_M, but on GTX 1080 Ti 11GB the best fitting quantization is Q2_K, which uses 13.0 GB.

What speed will Codestral 2 25.08 run at on GTX 1080 Ti 11GB?

On GTX 1080 Ti 11GB, Codestral 2 25.08 achieves approximately 13.7 tokens per second decode speed with a time-to-first-token of 14156ms using Q2_K quantization.

Can GTX 1080 Ti 11GB run Codestral 2 25.08 for coding?

For coding workloads, Codestral 2 25.08 on GTX 1080 Ti 11GB receives a F grade with 4.8 tok/s and 4K context.

What context window can Codestral 2 25.08 use on GTX 1080 Ti 11GB?

On GTX 1080 Ti 11GB, Codestral 2 25.08 can safely use up to 4K tokens of context at Q2_K quantization. The model's official context limit is 256K, but available memory constrains the safe maximum.

See all results for GTX 1080 Ti 11GB See all hardware for Codestral 2 25.08

Embed this result▼

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

<iframe src="https://willitrunai.com/embed/codestral-2-25.08-on-gtx-1080-ti-11gb" width="400" height="180" frameborder="0" style="border:none;border-radius:12px;overflow:hidden;" title="Will It Run AI — fit result"></iframe>

Preview: