Monitoring Embedding Drift in Production Scikit-LLM Pipelines

In this article, you will learn what embedding drift is, why it matters for production large language models, and how to implement two practical techniques to detect it.

Topics we will cover include:

• The key approaches for detecting embedding drift in production machine learning systems, including model-based detection, centroid distance, and dimensionality reduction combined with statistical tests.
• How to implement a domain classifier and a centroid distance method using scikit-learn on simulated 384-dimensional embeddings.
• How to apply these same drift detection techniques to real text embeddings generated with a SentenceTransformer model via Scikit-LLM.

Introduction

When a large language model (LLM) hits production, the story is far from over. User behavior inevitably evolves in the real world, and so does the data consumed by the model, typically encoded into numerical text representations called embeddings for its internal processing.

Therefore, it is crucial to track so-called embedding drifts to ascertain when a deployed model needs an update. However, traditional drift detection metrics designed for tabular data often fail when applied to high-dimensional embeddings.

This article starts by providing a brief outline of top techniques for detecting embedding drift, followed by an illustrative implementation of two of them, both simulation-based and in conjunction with the Scikit-LLM library for embedding generation.

Techniques for Effective Embedding Drift Detection

Below we list three key approaches for accurately identifying embedding drift that have been remarkably put into practice in production LLMs:

• Model-based detection: This consists of training a domain-specific classifier, usually a binary classifier that has learned to distinguish between baseline data and new (drifted) production data. A model capable of easily telling them apart will be able to signal drifts when they occur.
• Centroid distance: Following classical anomaly detection algorithms, this strategy boils down to calculating the distance (often cosine for embedding data) between the center of mass of your baseline embedding vectors and that of new, incoming embedding vectors.
• Combining dimensionality reduction and statistical tests: This method entails compressing the embeddings to a lower dimension using UMAP or PCA, after which we apply standard drift tests such as Kolmogorov-Smirnov.

Interested in exploring further how they work? Let’s examine how to implement the core logic behind two of these techniques based on an open-source stack.

Illustrating Drift Detection on Simulated Embeddings

Let’s build a mathematical foundation for two of the listed techniques using standard scikit-learn and simulated embeddings first. We generate an initial, random set of embeddings, after which we create another synthetic set — this time containing “production embeddings” that shift from the original embeddings’ mean to simulate the existence of data drift.

Next, we train a domain classifier based on random forests to separate baseline data (labeled 0) from new, production data (labeled 1). If the accuracy metric — for instance, ROC-AUC — signals a high value, e.g. above 0.65, the classifier will trigger a drift alert.

Output:

Alternatively, we can resort to the centroid calculation technique, also known as the “center of mass” method, measuring the distance between two centroids: one stemming from the baseline embeddings and one associated with the new, production embeddings. This method is computationally cheaper than the classifier method, but it incurs a loss of nuance (valuable information): after all, aggregating high-dimensional vectors into a single central point throws away complex distribution shapes, masking important patterns like multi-modal shifts or structural changes in the data.

Output:

No doubt the cosine distance value looks a bit exaggerated, due to a combination of the orthogonal nature of the distance metric used and the fact that the baseline data were generated randomly. A more realistic dataset would normally yield high distances in the presence of topic-driven data drifts, but not so extreme in the majority of cases. Let’s find out with a final example that uses Scikit-LLM to generate embeddings from real text.

Drift Detection on Generated Embeddings with Scikit-LLM

The last code example uses Scikit-LLM as a wrapper for a Groq LLM specialized in embedding generation. It has been run on Google Colab, with an API key obtained from Groq (a free LLM repository) and stored in the “My Secrets” section of the left-hand side menu.

The process is similar to what we saw earlier. The main difference lies in the data used, which are now embeddings generated from real text examples. Due to the intentionally drastic topic difference between the two datasets, the classifier can perfectly distinguish between baseline and production embeddings:

Let’s also try the centroid method one more time:

Output:

As we can see, financial/crypto topics and basic IT support can be far apart in the embedding space managed by our chosen model, all-MiniLM-L6-v2, which still yields a high cosine distance — although not nearly as high as in the purely random data scenario.

Wrapping Up

This article introduced some common techniques used in production machine learning systems to monitor and detect drifts in data represented as vector embeddings. Two of these techniques, namely model-based detection and the centroid distance method, have been illustrated through code examples, aided by Scikit-LLM for embedding generation.