Package: autoawq
AutoAWQ|Roadmap|Examples|Issues: Help Wanted|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 theoriginal workfrom MIT.Latest News🔥[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 availableInstallPrerequisitesNVIDIA: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 ROCm 5.6 or later.Install from PyPiTo install the newest AutoAWQ from PyPi, you need CUDA 12.1 installed.pip install autoawqBuild from sourceFor CUDA 11.8, ROCm 5.6, and ROCm 5.7, you can install wheels from therelease page:pip install autoawq@https://github.com/casper-hansen/AutoAWQ/releases/download/v0.2.0/autoawq-0.2.0+cu118-cp310-cp310-linux_x86_64.whlOr from the main branch directly:pip install autoawq@https://github.com/casper-hansen/AutoAWQ.gitOr by cloning the repository and installing from source:git clone https://github.com/casper-hansen/AutoAWQ
cd AutoAWQ
pip install -e .All three methods will install the latest and correct kernels for your system fromAutoAWQ_Kernels.If your system is not supported (i.e. not on the release page), you can build the kernels yourself by following the instructions inAutoAWQ_Kernelsand then install AutoAWQ from source.UsageUnder examples, you can find examples of how to quantize, run inference, and benchmark AutoAWQ models.INT4 GEMM vs INT4 GEMV vs FP16There 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-boundAt 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 modulesFused 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 withmodel.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 usefuse_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.Thepast_key_valuesfrommodel.generate()are only dummy values, so they cannot be used after generation.ExamplesMore examples can be found in theexamples directory.QuantizationExpect this to take 10-15 minutes on smaller 7B models, and around 1 hour for 70B models.fromawqimportAutoAWQForCausalLMfromtransformersimportAutoTokenizermodel_path='lmsys/vicuna-7b-v1.5'quant_path='vicuna-7b-v1.5-awq'quant_config={"zero_point":True,"q_group_size":128,"w_bit":4,"version":"GEMM"}# Load modelmodel=AutoAWQForCausalLM.from_pretrained(model_path)tokenizer=AutoTokenizer.from_pretrained(model_path,trust_remote_code=True)# Quantizemodel.quantize(tokenizer,quant_config=quant_config)# Save quantized modelmodel.save_quantized(quant_path)tokenizer.save_pretrained(quant_path)InferencefromawqimportAutoAWQForCausalLMfromtransformersimportAutoTokenizer,TextStreamerquant_path="TheBloke/zephyr-7B-beta-AWQ"# Load modelmodel=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 tokensprompt_template="""\


{prompt}

"""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.cuda()# Generate outputgeneration_output=model.generate(tokens,streamer=streamer,max_seq_len=512)BenchmarksThese 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.6GPU: RTX 4090 (AMD Ryzen 9 7950X)Command:python examples/benchmark.py --model_path <hf_model> --batch_size 1🟢 for GEMV, 🔵 for GEMM, 🔴 for avoid usingModel NameSizeVersionBatch SizePrefill LengthDecode LengthPrefill tokens/sDecode tokens/sMemory (VRAM)Vicuna7B🟢GEMV16464639.65198.8484.50 GB (19.05%)Vicuna7B🟢GEMV1204820481123.63133.1916.15 GB (26.02%)...........................Mistral7B🔵GEMM164641093.35156.3174.35 GB (18.41%)Mistral7B🔵GEMM1204820483897.02114.3555.55 GB (23.48%)Mistral7B🔵GEMM864644199.181185.254.35 GB (18.41%)Mistral7B🔵GEMM8204820483661.46829.75416.82 GB (71.12%)...........................Mistral7B🟢GEMV16464531.99188.294.28 GB (18.08%)Mistral7B🟢GEMV120482048903.83130.665.55 GB (23.48%)Mistral7B🔴GEMV86464897.87486.464.33 GB (18.31%)Mistral7B🔴GEMV820482048884.22411.89316.82 GB (71.12%)...........................TinyLlama1B🟢GEMV164641088.63548.9930.86 GB (3.62%)TinyLlama1B🟢GEMV1204820485178.98431.4682.10 GB (8.89%)...........................Llama 213B🔵GEMM16464820.3496.748.47 GB (35.83%)Llama 213B🔵GEMM1204820482279.4173.821310.28 GB (43.46%)Llama 213B🔵GEMM364641593.88286.2498.57 GB (36.24%)Llama 213B🔵GEMM3204820482226.7189.57316.90 GB (71.47%)...........................MPT7B🔵GEMM164641079.06161.3443.67 GB (15.51%)MPT7B🔵GEMM1204820484069.78114.9825.87 GB (24.82%)...........................Falcon7B🔵GEMM164641139.93133.5854.47 GB (18.92%)Falcon7B🔵GEMM1204820482850.97115.736.83 GB (28.88%)...........................CodeLlama34B🔵GEMM16464681.7441.0119.05 GB (80.57%)CodeLlama34B🔵GEMM1204820481072.3635.831620.26 GB (85.68%)...........................DeepSeek33B🔵GEMM164641160.1840.2918.92 GB (80.00%)DeepSeek33B🔵GEMM1204820481012.134.009319.87 GB (84.02%)Multi-GPUGPU: 2x NVIDIA GeForce RTX 4090ModelSizeVersionBatch SizePrefill LengthDecode LengthPrefill tokens/sDecode tokens/sMemory (VRAM)Mixtral46.7B🔵GEMM13232149.74293.40625.28 GB (53.44%)Mixtral46.7B🔵GEMM164641489.6493.18425.32 GB (53.53%)Mixtral46.7B🔵GEMM11281282082.9592.944425.33 GB (53.55%)Mixtral46.7B🔵GEMM12562562428.5991.518725.35 GB (53.59%)Mixtral46.7B🔵GEMM15125122633.1189.145725.39 GB (53.67%)Mixtral46.7B🔵GEMM1102410242598.9584.675325.75 GB (54.44%)Mixtral46.7B🔵GEMM1204820482446.1577.051627.98 GB (59.15%)Mixtral46.7B🔵GEMM1409640961985.7877.568934.65 GB (73.26%)ReferenceIf you find AWQ useful or relevant to your research, you can cite theirpaper:@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}
}