LLM

What GPU do I need to run LGAI-EXAONE/EXAONE-3.5-32B-Instruct?

A 32B language model for chat and instruction-following. 32.0B parameters, published in F32. View on Hugging Face

32.0B
Parameters
F32
Native precision
32K tokens (32,768)
Context length
Custom license
License
Text
Modality
LG AI Research
Organization

EXAONE-3.5-32B-Instruct is published by LGAI-EXAONE on Hugging Face, with 36,125 downloads and 130 likes to date. It's a ExaoneForCausalLM model built for text-generation, published natively in F32.

What EXAONE-3.5-32B-Instruct is

EXAONE-3.5-32B-Instruct is a 32B-parameter language model published by LG AI Research on Hugging Face. It is released under Custom license.

License note: a lab-specific license (tagged "other" on Hugging Face); read the model card's own license section before commercial use. Facts in this section are sourced from EXAONE-3.5-32B-Instruct's Hugging Face model card, not benchmarked by Aquanode.

What it's used for

  • Chat assistants
  • Instruction following
  • Synthetic data generation

VRAM required & cheapest live GPU fit

Required VRAM = weight size at each precision times a flat 1.2 overhead for activations and fragmentation. The KV-cache grows with context and is not in that factor; it is listed per model below where the architecture is published. Full formula and assumptions: methodology.

PrecisionWeight sizeRequired VRAMCheapest live fitGPUs neededEst. $/hr (full fit)
FP32119.2 GB143.1 GBAMD MI300X1$2.63/hr
cheaper alt.RTX A50006$1.06/hr
FP8 (quantized)29.8 GB35.8 GBL401$0.759/hr
cheaper alt.RTX 4000 Ada2$0.440/hr
INT4 (quantized)14.9 GB17.9 GBRTX A50001$0.176/hr

A GPU is only matched to a row if its hardware supports that precision, and the primary recommendation is always a single-GPU fit when one exists.

INT4 requires a quantized checkpoint actually published for this model, check its Hugging Face page before relying on this row.

Cheapest way to run EXAONE-3.5-32B-Instruct at its published (F32) precision: 1× AMD MI300X, at $2.63/hr per GPU ($2.63/hr total). Quantizing to FP8 or INT4 (rows above) can cost less, but requires a compatible quantized checkpoint to exist for this model.

EXAONE-3.5-32B-Instruct: KV cache by context length

The KV cache is the memory the attention layers hold for every token of context, on top of the weights. It is not part of the flat 1.2x overhead in the table above, grows with context length and with every concurrent request, and is why a long-context deployment needs more VRAM than the table shows.

Grouped-query attention: every layer caches keys and values for a few shared KV heads. Cached per token: 262,144 bytes at 16-bit.

ContextKV cache, one sequence
4K1.0 GB
32K8.0 GB

Computed from the layer, head and window counts in the model's own configuration (LGAI-EXAONE/EXAONE-3.5-32B-Instruct), at 16 bits per cached value. Each concurrent sequence needs its own cache, on top of the weights.

EXAONE-3.5-32B-Instruct: common questions

Can EXAONE-3.5-32B-Instruct run on a single GPU?

Yes, but not on a desktop card. At FP32 it needs 143.1 GB of VRAM, more than a single 32 GB desktop card holds. The cheapest live single-card fit is a 192.0 GB AMD MI300X at $2.63/hr.

Can EXAONE-3.5-32B-Instruct run in 16-bit instead of FP32?

Yes. Its published weights are FP32, 119.2 GB, or 143.1 GB once inference overhead is added. Loading the same weights in 16 bits halves that to 59.6 GB, or 71.5 GB with overhead. How much accuracy the cast costs is model-specific and is not measured here.

What is the least VRAM EXAONE-3.5-32B-Instruct can run in?

17.9 GB, at INT4 (quantized), which fits a 24 GB card, against 143.1 GB at FP32. That row assumes an INT4 checkpoint has actually been published for this model, so check its Hugging Face page before planning around it.

Does quantizing EXAONE-3.5-32B-Instruct lower the GPU bill?

Yes. At FP32 the cheapest live fit is one AMD MI300X at $2.63/hr. At INT4 (quantized) it drops to one RTX A5000 at $0.176/hr, provided a quantized checkpoint exists for it.

How to run EXAONE-3.5-32B-Instruct

Run EXAONE-3.5-32B-Instruct with vLLM

Generic example, not from the model's own docs: adjust flags (quantization, context length, parallelism) for your setup.

vllm serve LGAI-EXAONE/EXAONE-3.5-32B-Instruct --tensor-parallel-size 1

Run EXAONE-3.5-32B-Instruct with Ollama

Verified against Ollama's own library listing.

ollama run exaone3.5:32b

Source: https://ollama.com/library/exaone3.5:32b

Run EXAONE-3.5-32B-Instruct with GGUF quantizations

Prebuilt GGUF weights published at bartowski/EXAONE-3.5-32B-Instruct-GGUF. Run with llama.cpp's llama-server or load the repo directly in LM Studio.

llama-server -hf bartowski/EXAONE-3.5-32B-Instruct-GGUF

Source: https://huggingface.co/bartowski/EXAONE-3.5-32B-Instruct-GGUF

Deploy EXAONE-3.5-32B-Instruct on Aquanode

Aquanode has no one-click deploy template for EXAONE-3.5-32B-Instruct; you install the inference engine yourself with the commands below. Aquanode sells GPU pods billed per second, not a hosted inference API.

  1. Launch a bare GPU pod sized to the requirement above (1× AMD MI300X or larger).
  2. Open a terminal on the pod, or save one of the commands above as a startup script so it runs automatically the first time the pod boots.
  3. Run the command and connect to the resulting endpoint.
Launch a GPU pod

Weight-to-VRAM math, the fit rules, and how live prices are normalized: full methodology.

More EXAONE 3.5 models

All 4 EXAONE 3.5 models: VRAM and GPU requirements

Alternatives at this size

Other models for text-generation within about a third of EXAONE-3.5-32B-Instruct's 32.0B parameters, from other model lines.

More on EXAONE-3.5-32B-Instruct

Related reading: AMD MI300X pricing and specs, How much VRAM you need for LLMs, Serving LLMs with vLLM, vLLM vs TensorRT-LLM vs SGLang, and Best GPU for LLM inference.

Your own GPU cloud accounts

One console for the GPU clouds you already rent from. Your keys stay on your machine.

$20 a month, flat

Connect your accounts

One console for the GPU clouds you already use.

Connect your accounts for $20 a month, flat. Your provider bills the GPU.

© 2026 Aquanode. All rights reserved.

All trademarks, logos and brand names are the property of their respective owners.