Can starcoder2 15b instruct v0.1 run on GTX 1080 Ti 11GB?

BARELY — Tight on Memory

D38Poor
Estimated from fit model

starcoder2 15b instruct v0.1 needs ~12.9 GB VRAM. GTX 1080 Ti 11GB has 11.0 GB. With Q4_K_M quantization, expect ~16 tok/s.

Runtime: llama.cppCapacity: OffloadBandwidth: MediumStack: StandardBottleneck: 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) 12.9 GB, 16.0 tok/s, Very compromised (needs ~1.4 GB host RAM)
12.9 GB required11.0 GB available
117% VRAM needed

1.9 GB over capacity — needs offload or smaller quantization

Fit status

Very compromised (needs ~1.4 GB host RAM)

Decode

16.0 tok/s

TTFT

12083 ms

Safe context

4K

Memory

12.9 GB / 11.0 GB

Offload

10%

Memory breakdown

Weights9.2 GB
KV Cache1.8 GB
Runtime0.9 GB
Headroom1.1 GB

See how fast it feels

See how fast it feelsstarcoder2 15b instruct v0.1 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: 16.0 tok/s decode · 12.1s TTFT (warm) · 40 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.

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

Performance by workload

WorkloadGradeFitDecodeTTFTContext
ChatDVery compromised (needs ~0.8 GB host RAM)18.7 tok/s5645 ms4K
CodingDVery compromised (needs ~1.4 GB host RAM)16.0 tok/s12083 ms4K
Agentic CodingFToo heavy12.1 tok/s23264 ms4K
ReasoningDVery compromised (needs ~1.4 GB host RAM)16.0 tok/s14280 ms4K
RAGFToo heavy12.1 tok/s29080 ms4K

Inference speed

starcoder2 15b instruct v0.1 inference speed — tokens per second by GPU & Mac

Estimated decode speed (tokens/sec) for starcoder2 15b instruct v0.1 at Q4_K_M across popular GPUs and Apple Silicon, using the fastest local runtime per device. Fastest is RTX 5090 32GB at ~131 tok/s. Speed is memory-bandwidth bound, so cards that fit the whole model in VRAM run far faster than ones that offload to system RAM.

GPU / MacMemoryQuantSpeed (tok/s)Fits?
NVIDIARTX 5090 32GB
32 GBQ4_K_M131.2Fits
NVIDIARTX 4090 24GB
24 GBQ4_K_M83.7Fits
RX 7900 XTX 24GB
24 GBQ4_K_M75.5Fits
NVIDIARTX 3090 24GB
24 GBQ4_K_M71.6Fits
NVIDIARTX 4080 Super 16GB
16 GBQ4_K_M68.3Tight
Mac Studio M3 Ultra 256GB
256 GBQ4_K_M60.9Fits
Mac Studio M2 Ultra 128GB
128 GBQ4_K_M50.7Fits
Mac Studio M1 Ultra 128GB
128 GBQ4_K_M48.1Fits
MacBook Pro M4 Max 128GB
128 GBQ4_K_M34.7Fits
MacBook Pro M4 Max 64GB
64 GBQ4_K_M34.7Fits
NVIDIARTX 4070 12GB
12 GBQ4_K_M26.7Heavy offload
MacBook Pro M3 Max 64GB
64 GBQ4_K_M26.2Fits
MacBook Pro M1 Max 64GB
64 GBQ4_K_M24.0Fits
MacBook Pro M4 Pro 48GB
48 GBQ4_K_M21.2Fits
NVIDIARTX 3060 12GB
12 GBQ4_K_M15.7Heavy offload
NVIDIARTX 4060 8GB
8 GBQ4_K_M5.9Too big

Estimates for single-stream decoding at Q4_K_M; real tokens/sec varies with prompt length, context, batch size, and runtime build. Prompt processing (prefill) is faster than the decode figures shown here.

Quantization options

How starcoder2 15b instruct v0.1 (15B params) fits at each quantization level on GTX 1080 Ti 11GB (11.0 GB usable).

QuantBitsVRAMQualityFit
Q2_K
2
5.9 GB
LowC52
Q3_K_SBest for your GPU
3
7.4 GB
LowC51
NVFP4
4
8.4 GB
MediumF0
Q4_K_M
4
9.2 GB
MediumF0
Q5_K_M
5
10.8 GB
HighF0
Q6_K
6
12.3 GB
HighF0
Q8_0
8
16.1 GB
Very HighF0
F16
16
30.7 GB
MaximumF0

Get started

Copy-paste commands to run starcoder2 15b instruct v0.1 on your machine.

Run

lms load hf-lmstudio-community--starcoder2-15b-instruct-v0-1-gguf && lms server start

アップグレードオプション

starcoder2 15b instruct v0.1を快適に動かすハードウェア

Frequently asked questions

Can GTX 1080 Ti 11GB run starcoder2 15b instruct v0.1?

Yes, GTX 1080 Ti 11GB can run starcoder2 15b instruct v0.1 with a D grade (Very compromised (needs ~1.4 GB host RAM)). Expected decode speed: 16.0 tok/s.

How much VRAM does starcoder2 15b instruct v0.1 need?

starcoder2 15b instruct v0.1 (15B parameters) requires approximately 12.9 GB of memory with Q4_K_M quantization.

What is the best quantization for starcoder2 15b instruct v0.1?

The recommended quantization for starcoder2 15b instruct v0.1 is Q4_K_M, which balances quality and memory efficiency.

What speed will starcoder2 15b instruct v0.1 run at on GTX 1080 Ti 11GB?

On GTX 1080 Ti 11GB, starcoder2 15b instruct v0.1 achieves approximately 16.0 tokens per second decode speed with a time-to-first-token of 12083ms using Q4_K_M quantization.

Can GTX 1080 Ti 11GB run starcoder2 15b instruct v0.1 for coding?

For coding workloads, starcoder2 15b instruct v0.1 on GTX 1080 Ti 11GB receives a D grade with 16.0 tok/s and 4K context.

What context window can starcoder2 15b instruct v0.1 use on GTX 1080 Ti 11GB?

On GTX 1080 Ti 11GB, starcoder2 15b instruct v0.1 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 starcoder2 15b instruct v0.1 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.

See all results for GTX 1080 Ti 11GBSee all hardware for starcoder2 15b instruct v0.1
Embed this result

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

<iframe src="https://willitrunai.com/embed/hf-lmstudio-community--starcoder2-15b-instruct-v0-1-gguf-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: