Skip to content

Latest commit

 

History

History
74 lines (52 loc) · 5.45 KB

02-Advanced-Model-Loading-and-Best-Practice.md

File metadata and controls

74 lines (52 loc) · 5.45 KB
Raw

Advanced Model Loading and Best Practice

Welcome to the tutorial of AutoGPTQ, in this chapter, you will learn advanced model loading and best practice in auto-gptq.

Arguments Introduction

In previous chapter, you learned how to load model into CPU or single GPU with the two basic apis:

  • .from_pretrained: by default, load the whole pretrained model into CPU.
  • .from_quantized: by default, auto_gptq will automatically find the suitable way to load the quantized model.
    • if there is only single GPU and model can fit into it, will load the whole model into that GPU;
    • if there are multiple GPUs and model can fit into them, will evenly split model and load into those GPUs;
    • if model can't fit into GPU(s), will use CPU offloading.

However, the default settings above may not meet many users' demands, for they want to have more control of model loading.

Luckily, in AutoGPTQ, we provide some advanced arguments that users can tweak to manually config model loading strategy:

  • low_cpu_mem_usage: bool type argument, defaults to False, can be used both in .from_pretrained and .from_quantized, one can enable it when there is a limitation of CPU memory(by default model will be initialized in CPU) or want to load model faster.
  • max_memory: an optional List[Dict[Union[str, int], str]] type argument, can be used both in .from_pretrained and .from_quantized.
  • device_map: an optional Union[str, Dict[str, Union[int, str]]] type argument, currently only be supported in .from_quantized.

Before auto-gptq's existence, there are many users have already used other popular tools such as GPTQ-for-LLaMa to quantize their model and saved with different name without quantize_config.json file introduced in previous chapter.

To address this, two more arguments were introduced in .from_quantized so that users can load quantized model with arbitrary names.

  • quantize_config: an optional BaseQuantizeConfig type argument, can be used to match model file and initialize model incase quantize_config.json not in the directory where model is saved.
  • model_basename: an optional str type argument, if specified, will be used to match model instead of using the file name format introduced in previous chapter.

Multiple Devices Model Loading

max_memory

With this argument, you can specify how much memory for CPU and GPUs to use at most.

That means, by specify the maximum CPU memory used at model loading, you can load some model weights to CPU and picked into GPU only when they're required to be used, and back CPU again after that. This is called "CPU offload", a very useful strategy that used when there is no room left for quantization or inference if you keep the whole model in GPU(s).

Assume you have multiple GPUs, for each of them, you can also specify maximum memory that used to load model, separately. And by this, quantization and inference will be executed across devices.

To better understanding, below are some examples.

max_memory = {0: "20GIB"}

In this case, only first GPU (even if you have more GPUs) will be used to load model, and an error will be raised if the model requires memory over 20GB.

max_memory = {0: "20GIB", 1: "20GIB"}

In this case, you can load model that smaller than 40GB into two GPUs, and the model will be split evenly.

max_memory = {0: "10GIB", 1: "30GIB"}

In this case, you can also load model that smaller than 40GB into two GPUs, but the first GPU will use 10GB at most, which means if the model larger than 20GB, all model weights except the first 10GB will be loaded into the second GPU.

max_memory = {0: "20GIB", "cpu": "20GIB"}

In this case, you can also load model that smaller than 40GB but the rest 20GB will be kept in CPU memory, only be collected into GPU when needed.

device_map

So far, only .from_quantized supports this argument.

You can provide a string to this argument to use pre-set model loading strategies. Current valid values are ["auto", "balanced", "balanced_low_0", "sequential"]

In the simplest way, you can set device_map='auto' and let 🤗 Accelerate handle the device map computation. For more details of this argument, you can reference to this document.

Best Practice

At Quantization

It's always recommended to first consider loading the whole model into GPU(s) for it can save the time spend on transferring module's weights between CPU and GPU.

However, not everyone have large GPU memory. Roughly speaking, always specify the maximum memory CPU will be used to load model, then, for each GPU, you can preserve memory that can fit in 1~2(2~3 for the first GPU incase CPU offload used) model layers for examples' tensors and calculations in quantization, and load model weights using all others left. By this, all you need to do is a simple math based on the number of GPUs you have, the size of model weights file(s) and the number of model layers.

At Inference

For inference, following this principle: always using single GPU if you can, otherwise multiple GPUs, CPU offload is the last one to consider.

Conclusion

Congrats! You learned the advanced strategies to load model using .from_pretrained and .from_quantized in auto-gptq with some best practice advices. In the next chapter, you will learn how to quickly customize an AutoGPTQ model and use it to quantize and inference.