Data drift detection in MLOps - Time & Space Complexity

Time Complexity: Data drift detection

O(n)

Understanding Time Complexity

When detecting data drift, we want to know how the time to check changes as data grows.

We ask: How does the work increase when more data points arrive?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

# Assume we have a batch of new data samples
new_data = load_new_data()

# Reference data summary stored
ref_summary = load_reference_summary()

# For each feature, compare distributions
for feature in new_data.features:
    new_dist = calculate_distribution(new_data[feature])
    drift_score = compare_distributions(new_dist, ref_summary[feature])
    if drift_score > threshold:
        alert_drift(feature)

This code checks each feature's data distribution against a stored reference to find if data drift happened.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Loop over each feature to calculate and compare distributions.
• How many times: Once per feature in the dataset.

How Execution Grows With Input

As the number of features grows, the time to check drift grows linearly.

Input Size (n)	Approx. Operations
10 features	10 distribution comparisons
100 features	100 distribution comparisons
1000 features	1000 distribution comparisons

Pattern observation: Doubling features roughly doubles the work.

Final Time Complexity

Time Complexity: O(n)

This means the time to detect drift grows directly with the number of features checked.

Common Mistake

[X] Wrong: "Checking data drift takes the same time no matter how many features there are."

[OK] Correct: Each feature requires its own comparison, so more features mean more work.

Interview Connect

Understanding how data drift detection scales helps you design efficient monitoring systems in real projects.

Self-Check

"What if we compared only a random sample of features instead of all? How would the time complexity change?"

Practice

1. What is the main purpose of data drift detection in MLOps?

easy

A. To reduce the size of the dataset

B. To check if new data differs significantly from the training data

C. To improve the speed of model training

D. To increase the number of features in the model

Solution

1. Step 1: Understand data drift concept

   Data drift means the new data changes compared to the data used to train the model.

2. Step 2: Identify the purpose of detection

   Detecting data drift helps decide when to retrain or update the model to keep it accurate.

3. Final Answer:

   To check if new data differs significantly from the training data -> Option B

4. Quick Check:

   Data drift detection = check data difference [OK]

Hint: Data drift means new data changes from old data [OK]

Common Mistakes:

• Confusing data drift with model speed optimization
• Thinking data drift reduces dataset size
• Assuming data drift adds features

2. Which Python library is commonly used for detecting data drift in MLOps?

easy

A. Flask

B. NumPy

C. Matplotlib

D. Evidently

Solution

1. Step 1: Recall common MLOps tools

   Evidently is a popular tool designed specifically for monitoring data and model drift.

2. Step 2: Differentiate from other libraries

   NumPy is for math, Matplotlib for plotting, Flask for web apps, not for drift detection.

3. Final Answer:

   Evidently -> Option D

4. Quick Check:

   Evidently = data drift detection tool [OK]

Hint: Evidently is made for data drift detection [OK]

Common Mistakes:

• Choosing NumPy or Matplotlib which are not for drift detection
• Confusing Flask as a data tool

3. Given the code snippet using Evidently, what will report.run(reference_data, current_data) do?

medium

A. Visualize the model architecture

B. Train a new model on current_data

C. Compare current_data with reference_data to detect data drift

D. Delete old data from the system

Solution

1. Step 1: Understand Evidently report usage

   The run method compares new data (current_data) against reference data to find differences.

2. Step 2: Identify the purpose of the method

   It does not train models, visualize architecture, or delete data; it detects data drift.

3. Final Answer:

   Compare current_data with reference_data to detect data drift -> Option C

4. Quick Check:

   report.run compares data for drift [OK]

Hint: report.run compares new vs reference data [OK]

Common Mistakes:

• Thinking it trains a model
• Assuming it visualizes model structure
• Believing it deletes data

4. You wrote this code to detect data drift but get an error:

from evidently.dashboard import Dashboard
dashboard = Dashboard(tabs=["data_drift"])
dashboard.run(current_data)

What is the likely mistake?

medium

A. Missing reference data argument in dashboard.run()

B. Incorrect import statement for Dashboard

C. Dashboard does not support data_drift tab

D. current_data is not a valid variable name

Solution

1. Step 1: Check Dashboard.run() method requirements

   Dashboard.run() requires both reference and current datasets to compare for drift.

2. Step 2: Identify missing argument

   Only current_data is passed; reference_data is missing, causing the error.

3. Final Answer:

   Missing reference data argument in dashboard.run() -> Option A

4. Quick Check:

   Dashboard.run needs reference and current data [OK]

Hint: Dashboard.run needs two datasets: reference and current [OK]

Common Mistakes:

• Assuming import is wrong
• Thinking data_drift tab is unsupported
• Believing variable name causes error

5. You want to automate retraining your model when data drift is detected. Which approach best fits this goal?

hard

A. Set up a monitoring pipeline that runs data drift detection daily and triggers retraining if drift is found

B. Retrain the model every week regardless of data changes

C. Manually check data drift reports and retrain when you have time

D. Ignore data drift and only retrain when model accuracy drops

Solution

1. Step 1: Understand automation in MLOps

   Automating retraining based on data drift ensures the model stays accurate without manual checks.

2. Step 2: Identify best practice

   Running daily drift detection and triggering retraining only when drift occurs is efficient and effective.

3. Final Answer:

   Set up a monitoring pipeline that runs data drift detection daily and triggers retraining if drift is found -> Option A

4. Quick Check:

   Automate retrain on drift detection = best practice [OK]

Hint: Automate retrain triggered by drift detection [OK]

Common Mistakes:

• Retraining blindly without checking data
• Relying on manual checks only
• Ignoring drift until accuracy drops