Would CUDA be a better path than Intel Arc A730M 12GB for Codestral 22B v0.1 i1?

Often yes, if your goal is the easiest setup and the widest runtime support. Intel can offer attractive memory capacity, but CUDA still tends to win on tooling maturity, guides, kernels, and model coverage for local AI.

Can Codestral 22B v0.1 i1 run on Intel Arc A730M 12GB?

Q: What should I upgrade first if Codestral 22B v0.1 i1 feels slow on Intel Arc A730M 12GB?

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

D36Poor

Estimated from fit model

Codestral 22B v0.1 i1 needs ~13.3 GB VRAM. Intel Arc A730M 12GB has 12.0 GB. With Q2_K quantization, expect ~10 tok/s.

Runtime: llama.cppCapacity: OffloadBandwidth: LowStack: 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 22B v0.1 i1 at Q4_K_M needs 18.1 GB — too much for Intel Arc A730M 12GB (12.0 GB). Runs at Q2_K (13.3 GB) with low quality.

Capabilities:

Select quantization to explore

Q4_K_M (Medium quality) — 18.1 GB, exceeds 12.0 GB available

18.1 GB required12.0 GB available

151% VRAM needed

6.1 GB over capacity — needs offload or smaller quantization

Fit status

Too heavy

Decode

3.9 tok/s

TTFT

49969 ms

Safe context

Memory

18.1 GB / 12.0 GB

Offload

30%

Memory breakdown

Weights13.4 GB

KV Cache2.6 GB

Runtime0.9 GB

Headroom1.2 GB

See how fast it feels

With memory offload — actual speed may be lower

See how fast it feelsCodestral 22B v0.1 i1 on Intel Arc A730M 12GB
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: 3.9 tok/s decode · 50.0s TTFT (warm) · 10 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.

Runtime ecosystem is narrower than CUDA

Intel GPUs can look attractive on memory per dollar, but local AI tooling, kernels, and model coverage are still broader and easier on CUDA today.

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.

Prefer CUDA if you want the path of least resistance

If your goal is maximum runtime coverage, easier troubleshooting, and better support for new local AI releases, CUDA is usually still the safer upgrade path.

Buy headroom, not only minimum fit

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

Performance by workload

Workload	Grade	Fit	Decode	TTFT	Context
Chat	F	Too heavy	4.5 tok/s	23330 ms	4K
Coding	F	Too heavy	3.9 tok/s	49969 ms	4K
Agentic Coding	F	Too heavy	2.9 tok/s	96201 ms	4K
Reasoning	F	Too heavy	3.9 tok/s	59055 ms	4K
RAG	F	Too heavy	2.9 tok/s	120251 ms	4K

Quantization options

How Codestral 22B v0.1 i1 (22B params) fits at each quantization level on Intel Arc A730M 12GB (12.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 22B v0.1 i1 on your machine.

Run

lms load hf-mradermacher--codestral-22b-v0-1-i1-gguf && lms server start

Upgrade options

Hardware that runs Codestral 22B v0.1 i1 well

Intel Arc A770 16GBBest value

16 GB VRAM (+4)560 GB/s (+224)

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

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

Raises estimated decode speed by about 167%.

~$349 MSRP

Intel Arc Pro B50 16GBIntel upgrade

16 GB VRAM (+4)

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

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

Raises estimated decode speed by about 31%.

~$399 MSRP

Intel Arc Pro B60 24GBBudget pick

24 GB VRAM (+12)456 GB/s (+120)

Makes the model fit on the accelerator instead of staying completely out of reach.18.3 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.

~$599 MSRP

Frequently asked questions

Can Intel Arc A730M 12GB run Codestral 22B v0.1 i1?

Yes, Intel Arc A730M 12GB can run Codestral 22B v0.1 i1 at Q2_K quantization (Very compromised (needs ~0.8 GB host RAM)). The recommended Q4_K_M requires 18.1 GB which exceeds available memory, but at Q2_K it needs only 13.3 GB. Expected decode speed: 9.9 tok/s.

How much VRAM does Codestral 22B v0.1 i1 need?

Codestral 22B v0.1 i1 (22B parameters) requires approximately 18.1 GB at Q4_K_M quantization. On Intel Arc A730M 12GB, it fits at Q2_K using 13.3 GB.

What is the best quantization for Codestral 22B v0.1 i1?

The recommended quantization is Q4_K_M, but on Intel Arc A730M 12GB the best fitting quantization is Q2_K, which uses 13.3 GB.

What speed will Codestral 22B v0.1 i1 run at on Intel Arc A730M 12GB?

On Intel Arc A730M 12GB, Codestral 22B v0.1 i1 achieves approximately 9.9 tokens per second decode speed with a time-to-first-token of 19522ms using Q2_K quantization.

Can Intel Arc A730M 12GB run Codestral 22B v0.1 i1 for coding?

For coding workloads, Codestral 22B v0.1 i1 on Intel Arc A730M 12GB receives a F grade with 3.9 tok/s and 4K context.

What context window can Codestral 22B v0.1 i1 use on Intel Arc A730M 12GB?

On Intel Arc A730M 12GB, Codestral 22B v0.1 i1 can safely use up to 8K tokens of context at Q2_K quantization. The model's official context limit is —, but available memory constrains the safe maximum.

See all results for Intel Arc A730M 12GB See all hardware for Codestral 22B v0.1 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-22b-v0-1-i1-gguf-on-arc-a730m-12gb" width="400" height="180" frameborder="0" style="border:none;border-radius:12px;overflow:hidden;" title="Will It Run AI — fit result"></iframe>

Preview: