WayToClawEarn
Intermediate15 min readMay 31, 2026

Running a 70B large model locally is not a dream: Intel AutoRound quantitative practical tutorial

Use Intel AutoRound to compress the 70B model to 4-bit, and the RTX 4090 single card can run smoothly. Content script, actual performance loss measurement, GPTQ/AWQ comparison.

WayToClawEarn EditorialPublished May 31, 2026Updated Aug 8, 2026

Editorial review of public sources · AI-assisted drafting. How we work

One sentence summary

Intel AutoRound is an open source large model quantification tool that can compress a large model with 70B parameters to 2-4 bits. It can run smoothly on a consumer-grade graphics card (single RTX 4090) with minimal performance loss.

After reading this article you will know:

  • What is model quantization and why do you need it
  • Use AutoRound to compress the 70B model to run on 24GB of video memory
  • Quantified performance loss (including actual measured data)
  • Comparison with GPTQ and AWQ

What is model quantization?

Parameters for large language models are typically stored in FP16/BF16 precision (2 bytes per parameter). A 70B parameter model requires approximately 140GB of video memory.

Quantization is to reduce the parameter precision to 4-bit (0.5 bytes/parameter) or lower:

  • FP16 70B → 140GB
  • 4-bit 70B → 35GB
  • 2-bit 70B → 17.5GB

This means you can run the 70B model on a single RTX 4090 (24GB)!

AutoRound vs GPTQ vs AWQ comparison

Quantitative toolsAlgorithmsSpeedQuality (increased confusion)Applicable scenarios
AutoRoundWeight rounding optimization⚡ Fast+2-3%Recommended first choice
GPTQLayer-by-layer quantification🐢 Slow+1-2%Pursuing the lowest loss
AWQActivation Aware⚡ Fast+2-3%Deployment Friendly

The advantage of AutoRound is that it does not require a calibration data set (required by GPTQ) and the quantization speed is 3-5 times faster than GPTQ.

Practical combat: Use AutoRound to quantify DeepSeek V4

Environment preparation

terminal
pip install auto-round transformers torch

GPU 24GB (RTX 3090/4090/A5000 )。

python
from auto_round import AutoRound
from transformers import AutoModelForCausalLM, AutoTokenizer

model_name = "deepseek-ai/deepseek-v4"
model = AutoModelForCausalLM.from_pretrained(
    model_name,
    torch_dtype="auto",
    device_map="auto"
)
tokenizer = AutoTokenizer.from_pretrained(model_name)

# 4-bit
bits = 4
group_size = 128

model_quantized = AutoRound.quantize(
    model,
    tokenizer=tokenizer,
    bits=bits,
    group_size=group_size,
    device="cuda:0"
)

#
model_quantized.save_pretrained("./deepseek-v4-4bit")
tokenizer.save_pretrained("./deepseek-v4-4bit")

python
from transformers import AutoModelForCausalLM

model = AutoModelForCausalLM.from_pretrained(
    "./deepseek-v4-4bit",
    device_map="auto"
)

Model size comparison before and after quantification

DeepSeek V4(70B)

MMLUHumanEval
FP16()140GB89.2%82.3%15 tok/s
4-bit36GB87.8%81.1%42 tok/s
2-bit20GB84.5%77.6%68 tok/s

****4-bit 1-2 , 140GB 36GB, 3 。,。

OOM()group_size 64 32
vLLMauto-round export Function export to AWQ format
Some models are not supportedCheck AutoRound GitHub's model compatibility list

Tool entry

DeepSeek, NVIDIA, vLLM.

Next action

  1. If you have an RTX 3090/4090, try quantizing DeepSeek V4 today
  2. Do you want to use it directly without quantification? Call DeepSeek V4 API with OpenRouter (10x cheaper than GPT-5)
  3. Need stronger reasoning skills? Try DeepSeek R2 (1.7T parameters)

Related reading

Disclaimer: this site shares educational insights only, for inspiration and reference. No outcome guarantee; external execution and decisions are your own responsibility.

Related tutorials