Apache Airflow for ML orchestration in MLOps - Time & Space Complexity

Time Complexity: Apache Airflow for ML orchestration

O(n)

Understanding Time Complexity

When using Apache Airflow to run machine learning tasks, it's important to know how the time to complete workflows changes as you add more tasks.

We want to understand how the total work grows when the number of tasks increases.

Scenario Under Consideration

Analyze the time complexity of the following Airflow DAG code snippet.

from airflow import DAG
from airflow.operators.python import PythonOperator
from datetime import datetime

def train_model(task_id):
    print(f"Training model {task_id}")

dag = DAG('ml_training', start_date=datetime(2024, 1, 1))

n = 10  # Define n before using it

for i in range(1, n+1):
    task = PythonOperator(
        task_id=f'train_model_{i}',
        python_callable=lambda i=i: train_model(i),
        dag=dag
    )

This code creates a workflow with n training tasks, each running a model training step.

Identify Repeating Operations

• Primary operation: Creating and scheduling n training tasks in the DAG.
• How many times: The loop runs exactly n times, once per task.

How Execution Grows With Input

As you add more tasks, the total number of operations grows directly with the number of tasks.

Input Size (n)	Approx. Operations
10	10 task creations and schedules
100	100 task creations and schedules
1000	1000 task creations and schedules

Pattern observation: The work grows evenly and directly with the number of tasks added.

Final Time Complexity

Time Complexity: O(n)

This means the time to set up and schedule tasks grows in a straight line as you add more tasks.

Common Mistake

[X] Wrong: "Adding more tasks will only take a tiny bit more time, almost no change."

[OK] Correct: Each new task adds work to create and schedule it, so time grows steadily, not barely at all.

Interview Connect

Understanding how task count affects workflow time helps you design efficient ML pipelines and shows you can reason about scaling in real projects.

Self-Check

"What if tasks depended on each other in a chain instead of running independently? How would the time complexity change?"

Practice

1. What is the main purpose of Apache Airflow in ML orchestration?

easy

A. To store large datasets for ML training

B. To write ML model code in Python

C. To visualize ML model performance metrics

D. To automate and schedule ML workflows as directed tasks

Solution

1. Step 1: Understand Airflow's role

   Apache Airflow is designed to automate workflows by scheduling and running tasks in order.

2. Step 2: Differentiate from other ML tools

   It does not store data, visualize metrics, or write model code but manages task execution.

3. Final Answer:

   To automate and schedule ML workflows as directed tasks -> Option D

4. Quick Check:

   Airflow = workflow automation [OK]

Hint: Airflow schedules tasks, not data or model code [OK]

Common Mistakes:

• Confusing Airflow with data storage tools
• Thinking Airflow writes ML model code
• Assuming Airflow visualizes model metrics

2. Which of the following is the correct way to define a DAG in Apache Airflow using Python?

easy

A. dag = DAG('my_dag', run_every='daily')

B. dag = DAG('my_dag', schedule_interval='@daily')

C. dag = DAG('my_dag', interval='daily')

D. dag = DAG('my_dag', schedule='daily')

Solution

1. Step 1: Recall DAG initialization syntax

   The correct parameter to set schedule is schedule_interval, not run_every, interval, or schedule.

2. Step 2: Verify the example

   dag = DAG('my_dag', schedule_interval='@daily') is the standard syntax to schedule daily runs.

3. Final Answer:

   dag = DAG('my_dag', schedule_interval='@daily') -> Option B

4. Quick Check:

   Use schedule_interval to set DAG timing [OK]

Hint: Use schedule_interval to set DAG timing [OK]

Common Mistakes:

• Using incorrect parameter names like run_every
• Confusing schedule_interval with schedule
• Forgetting to use quotes around '@daily'

3. Given the following Airflow DAG snippet, what will be the order of task execution?

from airflow import DAG
from airflow.operators.python import PythonOperator
from datetime import datetime

def task_a():
    print('Task A')

def task_b():
    print('Task B')

def task_c():
    print('Task C')

dag = DAG('example_dag', start_date=datetime(2024, 1, 1), schedule_interval='@once')

t1 = PythonOperator(task_id='a', python_callable=task_a, dag=dag)
t2 = PythonOperator(task_id='b', python_callable=task_b, dag=dag)
t3 = PythonOperator(task_id='c', python_callable=task_c, dag=dag)

t1 >> t2 >> t3

medium

A. Task A, then Task B, then Task C

B. Task C, then Task B, then Task A

C. Task A, Task B, and Task C run in parallel

D. Task B, then Task A, then Task C

Solution

1. Step 1: Understand task dependencies

   The operator chaining t1 >> t2 >> t3 means t1 runs first, then t2, then t3.

2. Step 2: Confirm execution order

   Tasks print in order: Task A, Task B, Task C.

3. Final Answer:

   Task A, then Task B, then Task C -> Option A

4. Quick Check:

   Operator chaining sets task order [OK]

Hint: >> means run left task before right task [OK]

Common Mistakes:

• Assuming tasks run in parallel without dependencies
• Misreading the >> operator order
• Confusing task IDs with execution order

4. You wrote this Airflow DAG code but get an error: TypeError: DAG.__init__() got an unexpected keyword argument 'start'
What is the likely cause?

dag = DAG('my_dag', start='2024-01-01', schedule_interval='@daily')

medium

A. The parameter should be start_date, not start

B. The schedule_interval value '@daily' is invalid

C. DAG name cannot be 'my_dag'

D. Missing import for datetime module

Solution

1. Step 1: Identify incorrect parameter

   The error says start is unexpected; Airflow expects start_date.

2. Step 2: Confirm correct parameter usage

   Replacing start with start_date fixes the error.

3. Final Answer:

   The parameter should be start_date, not start -> Option A

4. Quick Check:

   Use start_date, not start [OK]

Hint: Use start_date, not start, for DAG start time [OK]

Common Mistakes:

• Using 'start' instead of 'start_date'
• Assuming '@daily' is invalid schedule
• Ignoring error message details

5. You want to create an Airflow DAG that runs an ML training task only if data preprocessing succeeded. Which Airflow feature should you use to enforce this dependency?

hard

A. Schedule both tasks to run at the same time

B. Use Airflow Variables to store task status

C. Set task dependencies using >> operator between preprocessing and training tasks

D. Write a single Python function combining both tasks

Solution

1. Step 1: Understand task dependency in Airflow

   Airflow uses task dependencies to control execution order, ensuring one task runs after another succeeds.

2. Step 2: Apply dependency operator

   Using the >> operator sets the training task to run only after preprocessing completes successfully.

3. Final Answer:

   Set task dependencies using >> operator between preprocessing and training tasks -> Option C

4. Quick Check:

   Use >> to enforce task order [OK]

Hint: Use >> to link tasks in order [OK]

Common Mistakes:

• Thinking Variables control task order
• Scheduling tasks simultaneously without dependencies
• Combining tasks loses modularity and control