AutoAWQ

| Roadmap | Examples | Issues: Help Wanted |

Supported by

AutoAWQ is an easy-to-use package for 4-bit quantized models. AutoAWQ speeds up models by 3x and reduces memory requirements by 3x compared to FP16. AutoAWQ implements the Activation-aware Weight Quantization (AWQ) algorithm for quantizing LLMs. AutoAWQ was created and improved upon from the original work from MIT.

Latest News 🔥

• [2024/06] CPU inference support (x86) - thanks Intel. Cohere and Phi3 support.
• [2024/04] StableLM and StarCoder2 support.
• [2024/03] Gemma support.
• [2024/02] PEFT-compatible training in FP16.
• [2024/02] AMD ROCm support through ExLlamaV2 kernels.
• [2024/01] Export to GGUF, ExLlamaV2 kernels, 60% faster context processing.
• [2023/12] Mixtral, LLaVa, QWen, Baichuan model support.
• [2023/11] AutoAWQ inference has been integrated into 🤗 transformers. Now includes CUDA 12.1 wheels.
• [2023/10] Mistral (Fused Modules), Bigcode, Turing support, Memory Bug Fix (Saves 2GB VRAM)
• [2023/09] 1.6x-2.5x speed boost on fused models (now including MPT and Falcon).
• [2023/09] Multi-GPU support, bug fixes, and better benchmark scripts available
• [2023/08] PyPi package released and AutoModel class available

Install

Prerequisites

• NVIDIA:
  • Your NVIDIA GPU(s) must be of Compute Capability 7.5. Turing and later architectures are supported.
  • Your CUDA version must be CUDA 11.8 or later.
• AMD:
  • Your ROCm version must be compatible with Triton.
• Intel CPU and Intel GPU:
  • Your torch and intel_extension_for_pytorch package version should at least 2.4 for optimized performance.

Install from PyPi

There are a few ways to install AutoAWQ:

1. Default:

   • pip install autoawq
   • NOTE: The default installation includes no external kernels and relies on Triton for inference.

2. From release with kernels:

   • pip install autoawq[kernels]
   • NOTE: This requires you to match the latest torch version that the kernels were build with.
   • NOTE: This installs https://github.com/casper-hansen/AutoAWQ_kernels

3. From main branch for Intel CPU and Intel XPU optimized performance:

   • pip install autoawq[cpu]
   • NOTE: Minimum of torch 2.4.0 is required.

Usage

Under examples, you can find examples of how to quantize, run inference, and benchmark AutoAWQ models.

INT4 GEMM vs INT4 GEMV vs FP16

There are two versions of AWQ: GEMM and GEMV. Both names relate to how matrix multiplication runs under the hood. We suggest the following:

• GEMV (quantized): 20% faster than GEMM, only batch size 1 (not good for large context).
• GEMM (quantized): Much faster than FP16 at batch sizes below 8 (good with large contexts).
• FP16 (non-quantized): Recommended for highest throughput: vLLM.

Compute-bound vs Memory-bound

At small batch sizes with small 7B models, we are memory-bound. This means we are bound by the bandwidth our GPU has to push around the weights in memory, and this is essentially what limits how many tokens per second we can generate. Being memory-bound is what makes quantized models faster because your weights are 3x smaller and can therefore be pushed around in memory much faster. This is different from being compute-bound where the main time spent during generation is doing matrix multiplication.

In the scenario of being compute-bound, which happens at higher batch sizes, you will not gain a speed-up using a W4A16 quantized model because the overhead of dequantization will slow down the overall generation. This happens because AWQ quantized models only store the weights in INT4 but perform FP16 operations during inference, so we are essentially converting INT4 -> FP16 during inference.

Fused modules

Fused modules are a large part of the speedup you get from AutoAWQ. The idea is to combine multiple layers into a single operation, thus becoming more efficient. Fused modules represent a set of custom modules that work separately from Huggingface models. They are compatible with model.generate() and other Huggingface methods, which comes with some inflexibility in how you can use your model if you activate fused modules:

• Fused modules are activated when you use fuse_layers=True.
• A custom cache is implemented. It preallocates based on batch size and sequence length.
  • You cannot change the sequence length after you have created your model.
  • Reference: AutoAWQForCausalLM.from_quantized(max_seq_len=seq_len, batch_size=batch_size)
• The main accelerator in the fused modules comes from FasterTransformer, which is only compatible with Linux.
• The past_key_values from model.generate() are only dummy values, so they cannot be used after generation.

Examples

More examples can be found in the examples directory.

from awq import AutoAWQForCausalLM
from transformers import AutoTokenizer

model_path = 'mistralai/Mistral-7B-Instruct-v0.2'
quant_path = 'mistral-instruct-v0.2-awq'
quant_config = { "zero_point": True, "q_group_size": 128, "w_bit": 4, "version": "GEMM" }

# Load model
model = AutoAWQForCausalLM.from_pretrained(model_path)
tokenizer = AutoTokenizer.from_pretrained(model_path, trust_remote_code=True)

# Quantize
model.quantize(tokenizer, quant_config=quant_config)

# Save quantized model
model.save_quantized(quant_path)
tokenizer.save_pretrained(quant_path)

print(f'Model is quantized and saved at "{quant_path}"')

from awq import AutoAWQForCausalLM
from transformers import AutoTokenizer, TextStreamer
from awq.utils.utils import get_best_device

device = get_best_device()

quant_path = "TheBloke/zephyr-7B-beta-AWQ"

# Load model
model = AutoAWQForCausalLM.from_quantized(quant_path, fuse_layers=True)
tokenizer = AutoTokenizer.from_pretrained(quant_path, trust_remote_code=True)
streamer = TextStreamer(tokenizer, skip_prompt=True, skip_special_tokens=True)

# Convert prompt to tokens
prompt_template = """\
<|system|>
</s>
<|user|>
{prompt}</s>
<|assistant|>"""

prompt = "You're standing on the surface of the Earth. "\
        "You walk one mile south, one mile west and one mile north. "\
        "You end up exactly where you started. Where are you?"

tokens = tokenizer(
    prompt_template.format(prompt=prompt), 
    return_tensors='pt'
).input_ids.to(device)

# Generate output
generation_output = model.generate(
    tokens, 
    streamer=streamer,
    max_seq_len=512
)

Benchmarks

These benchmarks showcase the speed and memory usage of processing context (prefill) and generating tokens (decoding). The results include speed at various batch sizes and different versions of AWQ kernels. We have aimed to test models fairly using the same benchmarking tool that you can use to reproduce the results. Do note that speed may vary not only between GPUs but also between CPUs. What matters most is a GPU with high memory bandwidth and a CPU with high single core clock speed.

• Tested with AutoAWQ version 0.1.6
• GPU: RTX 4090 (AMD Ryzen 9 7950X)
• Command: python examples/benchmark.py --model_path <hf_model> --batch_size 1
• 🟢 for GEMV, 🔵 for GEMM, 🔴 for avoid using

Multi-GPU

GPU: 2x NVIDIA GeForce RTX 4090

CPU

• CPU: 48 cores SPR (Intel 4th Gen Xeon CPU)
• Command: python examples/benchmark.py --model_path <hf_model> --batch_size 1 --generator hf

Reference

If you find AWQ useful or relevant to your research, you can cite their paper:

@article{lin2023awq,
  title={AWQ: Activation-aware Weight Quantization for LLM Compression and Acceleration},
  author={Lin, Ji and Tang, Jiaming and Tang, Haotian and Yang, Shang and Dang, Xingyu and Han, Song},
  journal={arXiv},
  year={2023}
}