Trigger-based retraining (schedule, drift, performance) in MLOps - Time & Space Complexity

Time Complexity: Trigger-based retraining (schedule, drift, performance)

O(n)

Understanding Time Complexity

When retraining machine learning models based on triggers like schedule, data drift, or performance, it's important to know how the time to decide and run retraining grows as data or checks increase.

We want to understand how the retraining process scales with more data and more frequent checks.

Scenario Under Consideration

Analyze the time complexity of the following retraining trigger check.

for batch in data_batches:
    drift_score = calculate_drift(batch)
    performance = evaluate_model(batch)
    if drift_score > drift_threshold or performance < perf_threshold:
        retrain_model()
        break
    wait_until_next_schedule()

This code checks each batch for drift and performance, triggers retraining if needed, or waits for the next scheduled check.

Identify Repeating Operations

Look at what repeats as input grows.

• Primary operation: Looping over data batches to calculate drift and evaluate performance.
• How many times: Once per batch until retraining triggers or all batches checked.

How Execution Grows With Input

As the number of data batches grows, the checks increase linearly.

Input Size (n)	Approx. Operations
10	About 10 drift and performance checks
100	About 100 checks
1000	Up to 1000 checks

Pattern observation: The number of operations grows directly with the number of batches checked.

Final Time Complexity

Time Complexity: O(n)

This means the time to decide on retraining grows in a straight line with the number of data batches checked.

Common Mistake

[X] Wrong: "Retraining checks happen instantly no matter how much data there is."

[OK] Correct: Each batch requires separate checks, so more batches mean more time spent before deciding.

Interview Connect

Understanding how retraining triggers scale helps you explain system responsiveness and efficiency in real projects.

Self-Check

What if we added parallel processing to check batches simultaneously? How would the time complexity change?

Practice

1. What is the main purpose of trigger-based retraining in machine learning operations?

easy

A. Automatically update models when data or performance changes

B. Manually retrain models on a fixed schedule

C. Store training data in a database

D. Visualize model performance metrics

Solution

1. Step 1: Understand trigger-based retraining concept

   Trigger-based retraining means models update automatically when certain conditions happen, like data changes or performance drops.

2. Step 2: Compare options to concept

   Only Automatically update models when data or performance changes describes automatic updates based on triggers, matching the concept.

3. Final Answer:

   Automatically update models when data or performance changes -> Option A

4. Quick Check:

   Trigger-based retraining = automatic updates [OK]

Hint: Triggers mean automatic updates, not manual tasks [OK]

Common Mistakes:

• Confusing manual retraining with trigger-based retraining
• Thinking triggers only store data
• Assuming triggers visualize data

2. Which SQL statement correctly creates a trigger to start retraining after new data is inserted into a table named training_data?

easy

A. CREATE retrain_trigger AFTER INSERT ON training_data CALL start_retraining();

B. INSERT TRIGGER retrain_trigger ON training_data AFTER EXEC start_retraining();"

C. TRIGGER CREATE retrain_trigger ON training_data AFTER INSERT EXEC start_retraining();

D. CREATE TRIGGER retrain_trigger AFTER INSERT ON training_data FOR EACH ROW EXECUTE PROCEDURE start_retraining();

Solution

1. Step 1: Recall correct SQL trigger syntax

   Standard SQL triggers use CREATE TRIGGER, specify timing (AFTER), event (INSERT), table, and procedure to execute.

2. Step 2: Match syntax to options

   CREATE TRIGGER retrain_trigger AFTER INSERT ON training_data FOR EACH ROW EXECUTE PROCEDURE start_retraining(); matches correct syntax: CREATE TRIGGER retrain_trigger AFTER INSERT ON training_data FOR EACH ROW EXECUTE PROCEDURE start_retraining();

3. Final Answer:

   CREATE TRIGGER retrain_trigger AFTER INSERT ON training_data FOR EACH ROW EXECUTE PROCEDURE start_retraining(); -> Option D

4. Quick Check:

   Correct trigger syntax = CREATE TRIGGER retrain_trigger AFTER INSERT ON training_data FOR EACH ROW EXECUTE PROCEDURE start_retraining(); [OK]

Hint: Look for 'CREATE TRIGGER ... EXECUTE PROCEDURE' pattern [OK]

Common Mistakes:

• Using CALL instead of EXECUTE PROCEDURE
• Wrong order of keywords
• Missing FOR EACH ROW clause

3. Given this trigger function in PostgreSQL:

CREATE OR REPLACE FUNCTION check_drift() RETURNS trigger AS $$
BEGIN
  IF NEW.error_rate > 0.1 THEN
    PERFORM start_retraining();
  END IF;
  RETURN NEW;
END;
$$ LANGUAGE plpgsql;

What happens when a new row with error_rate = 0.15 is inserted?

medium

A. The retraining procedure is called because error_rate > 0.1

B. Nothing happens because triggers don't run on INSERT

C. An error occurs due to syntax mistake

D. The row is rejected and not inserted

Solution

1. Step 1: Analyze trigger function logic

   The function checks if NEW.error_rate > 0.1; if true, it calls start_retraining().

2. Step 2: Apply condition to given data

   Since error_rate is 0.15, which is greater than 0.1, the retraining procedure is called.

3. Final Answer:

   The retraining procedure is called because error_rate > 0.1 -> Option A

4. Quick Check:

   error_rate 0.15 > 0.1 triggers retraining [OK]

Hint: Check condition in trigger function with inserted data [OK]

Common Mistakes:

• Thinking triggers don't run on INSERT
• Assuming syntax error without checking code
• Believing row insertion fails

4. You wrote this trigger to start retraining on performance drop:

CREATE TRIGGER retrain_on_drop
AFTER UPDATE ON model_metrics
FOR EACH ROW
WHEN (NEW.accuracy < OLD.accuracy)
EXECUTE PROCEDURE start_retraining();

But retraining never starts. What is the likely problem?

medium

A. Triggers cannot run AFTER UPDATE events

B. The WHEN clause is not supported in all SQL dialects

C. start_retraining() must be a procedure, not a function

D. The trigger name is invalid

Solution

1. Step 1: Understand WHEN clause support

   Not all SQL databases support the WHEN clause in triggers; some require condition checks inside the function.

2. Step 2: Identify why retraining doesn't start

   If the database ignores the WHEN clause, the condition is never checked, so retraining never triggers.

3. Final Answer:

   The WHEN clause is not supported in all SQL dialects -> Option B

4. Quick Check:

   WHEN clause support varies by SQL dialect [OK]

Hint: Check if your SQL dialect supports WHEN in triggers [OK]

Common Mistakes:

• Assuming triggers can't run AFTER UPDATE
• Confusing functions and procedures
• Thinking trigger names cause failure

5. You want to design a trigger-based retraining system that retrains a model only if both the data drift exceeds threshold and model accuracy drops below 90%. Which approach is best?

hard

A. Manually retrain the model when you notice performance issues

B. Create two separate triggers: one for drift and one for accuracy, each retraining independently

C. Create a trigger that calls a procedure checking both drift and accuracy before retraining

D. Schedule retraining daily regardless of drift or accuracy

Solution

1. Step 1: Understand combined condition requirement

   The retraining should happen only if both drift and accuracy conditions are met together.

2. Step 2: Evaluate options for combined logic

   Create a trigger that calls a procedure checking both drift and accuracy before retraining uses a single trigger calling a procedure that checks both conditions before retraining, ensuring both must be true.

3. Step 3: Why other options fail

   Create two separate triggers: one for drift and one for accuracy, each retraining independently retrains independently on each condition, not requiring both. Schedule retraining daily regardless of drift or accuracy ignores conditions. Manually retrain the model when you notice performance issues is manual, not trigger-based.

4. Final Answer:

   Create a trigger that calls a procedure checking both drift and accuracy before retraining -> Option C

5. Quick Check:

   Combined condition needs single trigger with logic [OK]

Hint: Use one trigger with combined condition check procedure [OK]

Common Mistakes:

• Using separate triggers causing unnecessary retraining
• Ignoring condition checks in triggers
• Relying on manual retraining only