Llama 3.3 70B fits on one rented GPU only when compressed. At 4-bit its file is 40 to 43 GB. A 48 GB card then runs it with short conversations, an 80 GB card with long ones.
Speed depends mostly on the card's memory bandwidth. By our calculation one H100 can write at most about 84 tokens a second at 4-bit. Real runs reach roughly half of such a limit.
The figures below come from Ollama's model files, NVIDIA's specifications and NVIDIA's own benchmark of this model, read on 27 October 2026.

Who this is for
- you want a 70B open model on hardware you control, without buying a GPU
- you are choosing between a 48 GB and an 80 GB card
- you want to know what speed to expect before you rent
Not for you if you only need the answers, not your own hardware: compare the costs in API, rented GPU or your own hardware.
Key numbers
- 43 GB Llama 3.3 70B at the usual 4-bit setting (q4_K_M) in Ollama's library Official page,
- 10.7 GB the extra memory one 32K-token conversation needs, at 16-bit cache Our calculation,
- 52 tokens per second for one user on two H100 cards at 8-bit, in NVIDIA's own benchmark Official page,
- 84 tokens per second the most one H100 SXM can write at 4-bit, from its memory bandwidth Our calculation,
What a 70B model needs at each precision
Ollama offers Llama 3.3 70B from 2-bit to full 16-bit. Each conversation also needs memory for its cache. Our GPU memory guide works out about 0.33 MB per token at 16-bit, or 10.7 GB for 32K tokens.
At 4-bit an 80 GB card holds the model and two 32K-token conversations; 8-bit needs a 94 GB card or more.
| Ollama tag | File size | Fits on, keeping 10% of the card free |
|---|---|---|
| 70b-instruct-q3_K_M (3-bit) | 34 GB | 48 GB, with conversations up to about 8K tokens |
| 70b-instruct-q4_0 (4-bit) | 40 GB | 48 GB with about 8K tokens; 80 GB with long conversations |
| 70b, the default (q4_K_M, 4-bit) | 43 GB | 80 GB, with two 32K-token conversations |
| 70b-instruct-q6_K (6-bit) | 58 GB | 80 GB, with one 32K-token conversation |
| 70b-instruct-q8_0 (8-bit) | 75 GB | 94 GB (H100 NVL) with short conversations; 141 GB (H200) with long ones |
| 70b-instruct-fp16 (16-bit) | 141 GB | two 80 GB cards or more |
Lower precision saves memory at some cost in quality. The 4-bit default is the usual compromise; 3-bit and 2-bit save more but lose more.
How fast it runs on one card
For one user, each new token means reading the whole model from the card's memory once. So the most tokens a second a card can write is its memory bandwidth divided by the size of the model file.
An H100's limit is about four times an L40S's, but real runs narrow the gap: the L40S uses more of its limit.
| Card | Memory bandwidth (GB/s) | Most tokens a second | Our estimate of real speed |
|---|---|---|---|
| NVIDIA L40S, 48 GB | 864 | 22 | about 16 |
| NVIDIA A100, 80 GB (SXM) | 2,039 | 51 | about 28 |
| NVIDIA H100, 80 GB (SXM) | 3,350 | 84 | about 45 |
| NVIDIA H100 NVL, 94 GB | 3,900 | 98 | about 53 |
| NVIDIA H200, 141 GB | 4,800 | 120 | about 65 |
Where does the estimate come from? NVIDIA's own benchmark ran Llama 3.3 70B at 8-bit across two H100 cards. For one user and a 5,000-token prompt, it measured 51.67 tokens a second and 0.41 seconds to the first token.
Each card held about 35 GB of the model there, so its limit was about 95 tokens a second. The measured speed is 54% of that, and we apply the same share to the H100, H200 and A100.
A 2024 benchmark on cards rented from RunPod backs this up. With Llama 3 70B at 4-bit in llama.cpp, an A100 SXM wrote 24 tokens a second, about half its limit.
The L40S wrote 15, about three-quarters of its limit, so we use that share for it (our calculation). Our speed figures by card list these runs and more.
Many users at once change the picture. Serving software such as vLLM or NVIDIA's NIM handles requests together. In the same benchmark, 50 users at once got about 814 tokens a second in total. Our comparison of vLLM, Ollama, llama.cpp and SGLang helps you pick the software.
Step by step with Ollama
Ollama is the quickest way to try the model on a rented card. Its documentation asks for an NVIDIA card with compute capability 5.0 or higher and driver 550 or newer, which every card above meets.
bash
nvidia-smi # the card, its memory and the driver
curl -fsSL https://ollama.com/install.sh | sh
ollama pull llama3.3:70b # 43 GB, 4-bit
ollama run llama3.3:70b "Summarise the main risks of running AI on your own server."
ollama ps # PROCESSOR should say 100% GPUOn a 48 GB card, pull llama3.3:70b-instruct-q4_0 instead, which is 40 GB. If ollama ps shows part of the model on the CPU, the card is too small for that file and the speed drops sharply.
Ollama answers one request per model at a time unless you raise OLLAMA_NUM_PARALLEL. Keep its port 11434 off the internet, as our guide to running Ollama explains.
Which rented GPU to pick
For one person or a small team, an 80 GB card is the comfortable choice. The default 4-bit file and long conversations fit with room to spare. A 48 GB card works for short jobs at 4-bit.
| Plan | Price | New-customer offer | Link |
|---|---|---|---|
| DigitalOcean GPU Droplet, 1 x NVIDIA L40S 48 GB GPU | $1.57/hour (about $1,146/month) on demand, billed per second · VAT not stated checked 25 Oct 2026 | New accounts get a $5 credit that lasts 90 days and covers every product except SaaS add-ons checked 29 Oct 2026 | Visit |
| UpCloud GPU Server, 1 x NVIDIA L40S, 8 cores, 64 GB 48 GB GPU | €1.11/hour (about €746/month; no charge after 28 days of use)30-day month: the last 2 days are free.31-day month: the last 3 days are free.February: no free days (one in a leap year).Started mid-month: it may never reach the cap that month. on demand, billed by the starting hour; monthly cost capped at 28 days of use checked 25 Oct 2026 | No offer | Visit |
| Liquid Web GPU server, NVIDIA L40S 48GB 48 GB GPU | $1,049.25/month monthly; 25% off the first month, then $1,399 · VAT not stated checked 25 Oct 2026 | No offer | Visit |
Monthly costs for hourly prices assume the server runs all month (730 hours), or less where a provider caps the monthly bill.
Hourly and per-second plans show the price for a full month; you pay only for the hours you use.
| Plan | Price | New-customer offer | Link |
|---|---|---|---|
| DigitalOcean GPU Droplet, 1 x NVIDIA H100 80 GB GPU | $4.41/hour (about $3,219/month) on demand, billed per second · VAT not stated checked 25 Oct 2026 | New accounts get a $5 credit that lasts 90 days and covers every product except SaaS add-ons checked 29 Oct 2026 | Visit |
| UpCloud GPU Server, 1 x NVIDIA H100, 12 cores, 240 GB 80 GB GPU | €2.17/hour (about €1,458/month; no charge after 28 days of use)30-day month: the last 2 days are free.31-day month: the last 3 days are free.February: no free days (one in a leap year).Started mid-month: it may never reach the cap that month. on demand, billed by the starting hour; monthly cost capped at 28 days of use checked 25 Oct 2026 | No offer | Visit |
| GPU Mart Enterprise Dedicated GPU Server - H100 80 GB GPU | $2,099/month monthly rate of a 24-month term, paid in advance · VAT not stated checked 25 Oct 2026 | A free 24-hour trial of a VPS, dedicated or GPU server for new clients, on request checked 29 Oct 2026 | Visit |
| GPU Mart Enterprise Dedicated GPU Server - A100(80GB) 80 GB GPU | $1,559/month monthly rate of a 24-month term, paid in advance · VAT not stated checked 25 Oct 2026 | A free 24-hour trial of a VPS, dedicated or GPU server for new clients, on request checked 29 Oct 2026 | Visit |
| Liquid Web GPU server, NVIDIA H100 NVL 94GB 94 GB GPU | $2,174.25/month monthly; 25% off the first month, then $2,899 · VAT not stated checked 25 Oct 2026 | No offer | Visit |
| Unihost AZM-10, NVIDIA H200 141 GB GPU | €2,999.90/month monthly, paid in advance; minimum one month checked 25 Oct 2026 | No offer | Visit |
Dedicated monthly servers suit steady use; hourly ones suit testing and bursts.
To compare a card with a model API, work out its cost per million tokens. Divide the hourly price by (tokens a second x 3,600), then multiply by 1,000,000. Our guide to API, rented GPU or your own hardware does this in full.
When two GPUs make more sense
Two cards make sense for 8-bit or 16-bit quality, for many users at once, or for very long documents. NVIDIA benchmarks this model on two H100 cards at 8-bit, and our price records include servers with two and eight H100 cards.
The licence
Llama 3.3 comes under Meta's Llama 3.3 Community License. It is free to use, but a service with more than 700 million monthly users needs Meta's permission. Meta also asks you to show "Built with Llama" where you use it.
How we checked
We read Ollama's model page and GPU documentation, NVIDIA's product pages and benchmark, and Meta's licence on 27 October 2026. The same day we read a 2024 benchmark on rented cards. The memory and speed sums are ours, set out above.
Our own measurements will be added here, with their dates, when our test bench runs them.
Mistakes to avoid
Renting a 24 GB card for a 70B model
Instead: Even the 2-bit file is 26 GB; start at 48 GB.
Filling the card to the brim
Instead: Leave room for each conversation's cache, about 0.33 MB per token.
Judging speed by the GPU's name alone
Instead: Memory bandwidth decides single-user speed.
Opening Ollama's port to the internet
Instead: Keep port 11434 on the server, or put a proxy with a password in front.
Other questions
How much VRAM does Llama 3.3 70B need?
About 40 to 43 GB at 4-bit, plus the conversation cache. That means a 48 GB card for short chats and an 80 GB card for long ones; at 8-bit the file alone is 75 GB.
Can Llama 3.3 70B run on a 24 GB card?
Not on the card alone: even Ollama's 2-bit file is 26 GB. Ollama can put part of the model on the processor instead, which is much slower.
How many tokens per second does Llama 3.3 70B reach?
On one H100 at 4-bit, about 45 for one user by our estimate. NVIDIA measured 52 on two H100 cards at 8-bit, and a 2024 benchmark measured 25 on an H100 PCIe at 4-bit.
Sources and test notes
- Ollama: llama3.3 tags and file sizes, read
- Ollama documentation: GPU support, read
- Ollama FAQ (parallel requests, context length), read
- NVIDIA NIM benchmarking: performance (Llama 3.3 70B Instruct), read
- NVIDIA H100, read
- NVIDIA H200, read
- NVIDIA A100, read
- NVIDIA L40S, read
- Meta: Llama 3.3 Community License, read
- GPU-Benchmarks-on-LLM-Inference on GitHub (llama.cpp on RunPod, May 2024), read
Every page read on 27 October 2026. Speed limits and estimates are our calculation from NVIDIA's bandwidth figures, NVIDIA's own benchmark and the 2024 benchmark on rented cards.