Skip to main content

What is the Impact of Quantisation on Memory Utilisation

 

AspectImpact on Memory Utilization
Large Language Models (LLMs)Reduced Model Size: Quantization reduces the number of bits used to represent each weight and activation. For example, converting from 32-bit floating point (FP32) to 8-bit integer (INT8) reduces memory usage by a factor of 4.

Lower Memory Footprint: This reduction in precision leads to a lower overall memory footprint for storing the model parameters and intermediate activations during inference and training. 

Increased Batch Sizes: With lower memory requirements, it becomes possible to process larger batch sizes within the same memory constraints, improving throughput.
Vector DatabasesCompact Embeddings: Quantization reduces the size of vector embeddings stored in the database. For instance, converting vectors from 32-bit to 8-bit representation decreases storage requirements by up to 75%. 

Efficient Indexing: Smaller vector sizes allow for more efficient indexing and faster retrieval operations due to reduced memory bandwidth and cache usage. 

Scalability: The reduction in memory usage enables the handling of larger datasets and more vectors within the same hardware constraints, improving the scalability of the system.

Benefits of Reduced Memory Utilization

  • Cost Efficiency: Lower memory usage translates to reduced hardware costs, as less RAM and storage are required.
  • Energy Efficiency: Less memory usage often results in lower power consumption, contributing to energy efficiency.
  • Performance Improvements: Reduced memory usage can lead to faster data access and processing times, as more data can fit into the faster levels of the memory hierarchy (e.g., caches).
  • Deployment Flexibility: Models and databases with lower memory footprints can be deployed on a wider range of devices, including edge devices with limited resources.
Labels:

Comments

Post a Comment

Popular posts from this blog

What is Tensor Parallelism and relationship between Buffer and GPU

  Tensor Parallelism in GPU Tensor parallelism is a technique used to distribute the computation of large tensor operations across multiple GPUs or multiple cores within a GPU .   It is an essential method for improving the performance and scalability of deep learning models, particularly when dealing with very large models that cannot fit into the memory of a single GPU. Key Concepts Tensor Operations : Tensors are multidimensional arrays used extensively in deep learning. Common tensor operations include matrix multiplication, convolution, and element-wise operations. Parallelism : Parallelism involves dividing a task into smaller sub-tasks that can be executed simultaneously. This approach leverages the parallel processing capabilities of GPUs to speed up computations. How Tensor Parallelism Works Splitting Tensors : The core idea of tensor parallelism is to split large tensors into smaller chunks that can be processed in parallel. Each chunk is assigned to a different GP...
Post a Comment
Read more

Data Wrangling vs EDA

  Aspect Data Wrangling (Data Preprocessing) Exploratory Data Analysis (EDA) Objective Prepare raw data for modeling by cleaning, transforming, and formatting it appropriately. Explore and understand the data to gain insights, identify patterns, and make decisions on data handling and modeling. Order Typically performed as a preliminary step before EDA. Usually conducted after data wrangling to further investigate data characteristics. Data Handling Focuses on data cleaning, filling missing values, encoding categorical variables, and scaling features. Involves data visualization, statistical analysis, and summary statistics to uncover patterns, relationships, and anomalies. Techniques Techniques include imputation, outlier detection, feature scaling, and one-hot encoding. Techniques include histograms, scatter plots, box plots, correlation matrices, and descriptive statistics. Data Transformation Involves structural changes to the dataset, such as feature engineering, data normaliz...
Post a Comment
Read more

What's replicated, what's not?

Logged operations are replicated. These include, but are not limited to: DDL DML Create/alter table space Create/alter storage group Create/alter buffer pool XML data. Logged LOBs Not logged operations are not replicated. These include, but are not limited to: Database configuration parameters (this allows primary and standby databases to be configured differently). "Not logged initially" tables Not logged LOBs UDF (User Defined Function) libraries. UDF DDL is replicated. But the libraries used by UDF (such as C or Java libraries)  are not replicated, because they are not stored in the database. Users must manually copy the libraries to the standby. Note: You can use database configuration parameter  BLOCKNONLOGGED  to block not logged operations on the primary.
Post a Comment
Read more