Content provided by Nicolay Gerold. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Nicolay Gerold or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://ppacc.player.fm/legal.
Player FM - Podcast App
Go offline with the Player FM app!
icon Daily Deals

#040 Vector Database Quantization, Product, Binary, and Scalar

52:12
 
Share
 

Manage episode 464211047 series 3585930
Content provided by Nicolay Gerold. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Nicolay Gerold or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://ppacc.player.fm/legal.

When you store vectors, each number takes up 32 bits.

With 1000 numbers per vector and millions of vectors, costs explode.

A simple chatbot can cost thousands per month just to store and search through vectors.

The Fix: Quantization

Think of it like image compression. JPEGs look almost as good as raw photos but take up far less space. Quantization does the same for vectors.

Today we are back continuing our series on search with Zain Hasan, a former ML engineer at Weaviate and now a Senior AI/ ML Engineer at Together. We talk about the different types of quantization, when to use them, how to use them, and their tradeoff.

Three Ways to Quantize:

  1. Binary Quantization
    • Turn each number into just 0 or 1
    • Ask: "Is this dimension positive or negative?"
    • Works great for 1000+ dimensions
    • Cuts memory by 97%
    • Best for normally distributed data
  2. Product Quantization
    • Split vector into chunks
    • Group similar chunks
    • Store cluster IDs instead of full numbers
    • Good when binary quantization fails
    • More complex but flexible
  3. Scalar Quantization
    • Use 8 bits instead of 32
    • Simple middle ground
    • Keeps more precision than binary
    • Less savings than binary

Key Quotes:

  • "Vector databases are pretty much the commercialization and the productization of representation learning."
  • "I think quantization, it builds on the assumption that there is still noise in the embeddings. And if I'm looking, it's pretty similar as well to the thought of Matryoshka embeddings that I can reduce the dimensionality."
  • "Going from text to multimedia in vector databases is really simple."
  • "Vector databases allow you to take all the advances that are happening in machine learning and now just simply turn a switch and use them for your application."

Zain Hasan:

Nicolay Gerold:

vector databases, quantization, hybrid search, multi-vector support, representation learning, cost reduction, memory optimization, multimodal recommender systems, brain-computer interfaces, weather prediction models, AI applications

  continue reading

53 episodes

iconShare
 
Manage episode 464211047 series 3585930
Content provided by Nicolay Gerold. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Nicolay Gerold or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://ppacc.player.fm/legal.

When you store vectors, each number takes up 32 bits.

With 1000 numbers per vector and millions of vectors, costs explode.

A simple chatbot can cost thousands per month just to store and search through vectors.

The Fix: Quantization

Think of it like image compression. JPEGs look almost as good as raw photos but take up far less space. Quantization does the same for vectors.

Today we are back continuing our series on search with Zain Hasan, a former ML engineer at Weaviate and now a Senior AI/ ML Engineer at Together. We talk about the different types of quantization, when to use them, how to use them, and their tradeoff.

Three Ways to Quantize:

  1. Binary Quantization
    • Turn each number into just 0 or 1
    • Ask: "Is this dimension positive or negative?"
    • Works great for 1000+ dimensions
    • Cuts memory by 97%
    • Best for normally distributed data
  2. Product Quantization
    • Split vector into chunks
    • Group similar chunks
    • Store cluster IDs instead of full numbers
    • Good when binary quantization fails
    • More complex but flexible
  3. Scalar Quantization
    • Use 8 bits instead of 32
    • Simple middle ground
    • Keeps more precision than binary
    • Less savings than binary

Key Quotes:

  • "Vector databases are pretty much the commercialization and the productization of representation learning."
  • "I think quantization, it builds on the assumption that there is still noise in the embeddings. And if I'm looking, it's pretty similar as well to the thought of Matryoshka embeddings that I can reduce the dimensionality."
  • "Going from text to multimedia in vector databases is really simple."
  • "Vector databases allow you to take all the advances that are happening in machine learning and now just simply turn a switch and use them for your application."

Zain Hasan:

Nicolay Gerold:

vector databases, quantization, hybrid search, multi-vector support, representation learning, cost reduction, memory optimization, multimodal recommender systems, brain-computer interfaces, weather prediction models, AI applications

  continue reading

53 episodes

All episodes

×
 
Loading …

Welcome to Player FM!

Player FM is scanning the web for high-quality podcasts for you to enjoy right now. It's the best podcast app and works on Android, iPhone, and the web. Signup to sync subscriptions across devices.

 

icon Daily Deals
icon Daily Deals
icon Daily Deals

Quick Reference Guide

Listen to this show while you explore
Play