Skip to content
Launch imminent

Official date to be announced shortlyGPU offers available at launch; figures shown are indicative.

Priority access: sign up

GPUs for LLM inference

Serving a language model has two limits: the weights and the KV cache must fit in GPU memory, and each generated token reads the weights from memory again. Memory size decides which models you can serve; memory bandwidth largely decides how fast they answer.

GPUs that fit LLM inference

Swipe sideways to see every column.

GPUs suited to LLM inference: manufacturer specifications per GPU, cautious estimates and best live price per GPU-hour excluding tax
GPUMemoryBandwidthFP8 tensorInference, 16-bitInference, 4-bitPrice/h
L4Ada Lovelace24 GB300 GB/s242 TFLOPS≈ 9B≈ 30Bfrom $0.44
RTX 4090Ada Lovelace24 GB1,008 GB/sNot published≈ 9B≈ 30Bfrom $0.33
RTX 5090Blackwell32 GB1,792 GB/sNot published≈ 10B≈ 40Bfrom $0.69
L40SAda Lovelace48 GB864 GB/s733 TFLOPS≈ 15B≈ 60Bfrom $0.79
RTX PRO 6000 BlackwellBlackwell96 GB1,792 GB/sNot published≈ 35B≈ 120Bfrom $1.69
A100 SXMAmpere80 GB2,039 GB/sNot published≈ 30B≈ 100Bfrom $1.79
H100 SXMHopper80 GB3,350 GB/s1,979 TFLOPS≈ 30B≈ 100Bfrom $2.88
H200Hopper141 GB4,800 GB/s1,979 TFLOPS≈ 55B≈ 180Bfrom $4.19
MI300XCDNA 3192 GB5,300 GB/s2,614 TFLOPS≈ 75B≈ 250Bfrom $4.16

Manufacturer specifications, per GPU; tensor throughput without sparsity. Model sizes are cautious estimates in billions of parameters, counting 80% of memory; context length, batch size and framework change the real limit. Prices are the best live offer for one GPU per hour, excluding tax.

All GPU models

What matters for LLM inference

  1. Fit the model, then the cache

    A model needs about 2 bytes per parameter in 16-bit and about half a byte in 4-bit quantization. The KV cache grows with context length and the number of concurrent requests, which is why the estimates keep 20% of memory free.

  2. Bandwidth drives tokens per second

    At small batch sizes, token generation is bound by memory bandwidth, not compute: a GPU with twice the bandwidth generates tokens roughly twice as fast on the same model. Compare the bandwidth column first for chat and agent workloads.

  3. Throughput and FP8

    For batch jobs and high concurrency, tensor throughput matters more. Hopper, Ada Lovelace and newer GPUs support FP8, which halves the memory of the weights compared with 16-bit and speeds up serving engines that support it.

Compare GPUs for LLM inference

GPUs for LLM inference: frequently asked questions

Which GPU do I need to run a 70B model?

In 4-bit quantization, a 70-billion-parameter model needs roughly 40 GB for the weights alone: a single 48 GB GPU is tight, an 80 GB GPU leaves room for the cache. In 16-bit it needs about 140 GB for the weights, so at least two 80 GB GPUs.

Is an RTX 4090 good for inference?

For models up to about 30 billion parameters in 4-bit, yes: it has 24 GB of memory and about 1 TB/s of bandwidth. Larger models and long contexts need more memory per GPU.

Should I quantize my model?

Quantization to 8-bit or 4-bit lets a larger model fit and usually speeds up generation, with a small loss of quality that depends on the model and method. Test the quality on your own prompts before serving.

How do I rent a GPU for LLM inference on EverXCloud?

Create an account, top up your prepaid balance in euros, US dollars or pounds, then buy GPU hours on the spot exchange at the best offer, or place a request at the price you are willing to pay. Rentals are billed by the hour. Prices are shown excluding tax and EverXCloud is the merchant of record for every rental.

Check the workload, complete configuration and billing conditions before choosing a live offer.

Be ready on launch day

Create your account now: you can top up your balance and rent the GPU that fits your workload as soon as the market opens.

Have GPU servers?

Businesses can join the EverXCloud Network and sell hours of their GPU servers on the spot exchange.

Become a supplier