Code Llama 70B Instruct on NVIDIA L40S
Can the NVIDIA L40S run Code Llama 70B Instruct?
Yes, it runs well
Runs well. At Q3_K_M it needs about 38.1 GB of 48.0 GB usable, with an estimated speed of 19.9 tok/s.
- Best quant
Q3_K_M- Generation speed
- 19.9 tok/s
- Prompt processing
- 956 tok/s
- First token (1K prompt)
- 1.1 s
- Largest safe context
- 4K
Best app to run it on the NVIDIA L40S
On Linux
- One command with Ollama’s own build of this model.
- Serves an OpenAI-compatible API that other apps and coding tools can use.
ollama run codellama:70b-instruct-q3_K_MOn Windows
- One command with Ollama’s own build of this model.
- Serves an OpenAI-compatible API that other apps and coding tools can use.
ollama run codellama:70b-instruct-q3_K_MDownload Code Llama 70B Instruct
Recommended for the NVIDIA L40S: Q3_K_M. Every other quantization has its own download link in the table below.
Quickest · Ollama
One command downloads a ready-to-run version and starts a chat.
ollama run codellama:70b-instruct-q3_K_MQuantized files · GGUF
Works in LM Studio, llama.cpp, Jan and Ollama. No sign-in needed.
Download the Q3_K_M file (opens in a new tab)
huggingface.co/TheBloke/CodeLlama-70B-Instruct-GGUF (opens in a new tab)
ollama run hf.co/TheBloke/CodeLlama-70B-Instruct-GGUF:Q3_K_MOriginal weights · Hugging Face
Full-precision files from Meta, for fine-tuning, vLLM, Transformers.
huggingface.co/meta-llama/CodeLlama-70b-Instruct-hf (opens in a new tab)
Official repo · GitHub
Reference code, inference scripts and docs from Meta. The weights themselves download from Hugging Face.
github.com/meta-llama/codellama (opens in a new tab)
git clone https://github.com/meta-llama/codellamaHow it’s rated
Match score
To order lists, each result also gets a match score out of 100 from four parts. It favors the most capable model that still runs well.
| Model quality | 16.6 / 45 | |
|---|---|---|
| Memory fit | 25.0 / 25 | |
| Speed | 10.6 / 15 | |
| Memory use | 15.0 / 15 | |
| Match score | 67.2 / 100 |
Every quantization on the NVIDIA L40S
| Quant | Memory needed | Available | Speed | Runs | Quality | Download |
|---|---|---|---|---|---|---|
Q2_K | 31.9 GB | 48.0 GB | 25.3 tok/s | Runs well | 30Basic quality (D) · 30 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 65/100 (quality, fit, speed and memory use) sets the ranking. | GGUF (opens in a new tab) |
Q3_K_M | 38.1 GB | 48.0 GB | 19.9 tok/s | Runs well | 36Basic quality (D) · 36 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 67/100 (quality, fit, speed and memory use) sets the ranking. | GGUF (opens in a new tab) |
Q4_K_M | 46.4 GB | 48.0 GB | 15.4 tok/s | Runs welltight fit | 41Fair quality (C) · 41 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 67/100 (quality, fit, speed and memory use) sets the ranking. | GGUF (opens in a new tab) |
Q5_K_M | 53.3 GB | 48.0 GB | 5.5 tok/s | Slowoffloads to RAM | 42Fair quality (C) · 42 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 49/100 (quality, fit, speed and memory use) sets the ranking. | GGUF (opens in a new tab) |
Q6_K | 60.9 GB | 48.0 GB | 2.9 tok/s | Very slowoffloads to RAM | 43Fair quality (C) · 43 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 48/100 (quality, fit, speed and memory use) sets the ranking. | |
Q8_0 | 77.5 GB | 48.0 GB | — | Won't run | 44Fair quality (C) · 44 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 5/100 (quality, fit, speed and memory use) sets the ranking. | |
F16 | 142 GB | 48.0 GB | — | Won't run | 44Fair quality (C) · 44 of 100: how capable the model is at F16, whatever it runs on. Match score 5/100 (quality, fit, speed and memory use) sets the ranking. | Original weights (opens in a new tab) |
Memory figures assume 4K of context. Longer conversations or documents grow the KV cache.
Other hardware that runs it
-
41Fair quality (C) · 41 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 68/100 (quality, fit, speed and memory use) sets the ranking.
NVIDIA RTX PRO 6000 Blackwell
-
30Basic quality (D) · 30 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 67/100 (quality, fit, speed and memory use) sets the ranking.
NVIDIA GeForce RTX 5090
-
36Basic quality (D) · 36 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 64/100 (quality, fit, speed and memory use) sets the ranking.
Apple M4 Max (64 GB)
-
30Basic quality (D) · 30 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 61/100 (quality, fit, speed and memory use) sets the ranking.
Apple M1 Max (64 GB)
-
41Fair quality (C) · 41 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 61/100 (quality, fit, speed and memory use) sets the ranking.
Apple M2 Ultra (192 GB)
-
36Basic quality (D) · 36 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 59/100 (quality, fit, speed and memory use) sets the ranking.
Apple M4 Max (128 GB)
Quick answers
How much memory does Code Llama 70B Instruct need on the NVIDIA L40S 48GB?
At Q3_K_M it needs about 38.1 GB. The NVIDIA L40S 48GB has 48.0 GB usable.
How fast is Code Llama 70B Instruct on the NVIDIA L40S 48GB?
About 19.9 tok/s at Q3_K_M, an estimate from the hardware’s memory bandwidth and the size of the model.
Which quantization of Code Llama 70B Instruct should I use on the NVIDIA L40S 48GB?
Q3_K_M. Of the versions that fit, it is the one that runs best; when two run equally well, the check prefers the higher-rated one.
Estimates come from published hardware specs and our open formulas, not from running the model on your machine. Real speed varies with runtime, drivers and settings. Numbers marked “Measured” come from a linked benchmark.