Cost optimization at scale in MLOps - Time & Space Complexity

Time Complexity: Cost optimization at scale

O(n x m)

Understanding Time Complexity

When managing machine learning operations at scale, it's important to understand how the cost of running tasks grows as the workload increases.

We want to know how the time and resources needed change when we handle more data or models.

Scenario Under Consideration

Analyze the time complexity of the following cost calculation process.

for model in deployed_models:
    for data_batch in incoming_data:
        cost += compute_cost(model, data_batch)

This code calculates the total cost by checking each deployed model against each batch of incoming data.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Nested loops over models and data batches.
• How many times: For each model, it processes every data batch.

How Execution Grows With Input

As the number of models or data batches grows, the total cost calculations increase quickly.

Input Size (models x data batches)	Approx. Operations
10 x 10	100
100 x 100	10,000
1000 x 1000	1,000,000

Pattern observation: Doubling both inputs causes the operations to grow by four times, showing a fast increase.

Final Time Complexity

Time Complexity: O(n * m)

This means the time needed grows proportionally to the number of models times the number of data batches.

Common Mistake

[X] Wrong: "The cost grows only with the number of models or data batches, not both together."

[OK] Correct: Because the code checks every model with every data batch, both inputs multiply the work, not just one.

Interview Connect

Understanding how nested operations affect cost helps you explain and improve real-world ML system efficiency.

Self-Check

"What if we processed only a fixed number of data batches per model regardless of total batches? How would the time complexity change?"

Practice

1. What is the main goal of cost optimization at scale in MLOps?

easy

A. To increase the number of servers regardless of workload

B. To avoid monitoring costs after deployment

C. To use only the most expensive cloud resources

D. To save money by matching resource use to workload needs

Solution

1. Step 1: Understand cost optimization purpose

   Cost optimization means using resources efficiently to reduce expenses.

2. Step 2: Match resources to workload needs

   Adjusting resources based on workload avoids waste and saves money.

3. Final Answer:

   To save money by matching resource use to workload needs -> Option D

4. Quick Check:

   Cost optimization = save money by matching resources [OK]

Hint: Cost optimization means using just enough resources [OK]

Common Mistakes:

• Thinking more servers always means better
• Ignoring cost monitoring after deployment
• Assuming expensive resources are always best

2. Which of the following is a correct way to specify a spot instance in a Kubernetes pod spec for cost savings?

easy

A. affinity:
nodeAffinity:
requiredDuringSchedulingIgnoredDuringExecution:
nodeSelectorTerms:
- matchExpressions:
- key: "kubernetes.io/lifecycle"
operator: In
values:
- spot

B. tolerations:
- key: "spot-instance"
operator: Exists
effect: NoSchedule

C. nodeSelector:
kubernetes.io/instance-type: spot

D. resources:
requests:
cpu: "spot"
memory: "spot"

Solution

1. Step 1: Understand spot instance labeling in Kubernetes

   Spot instances are often labeled with lifecycle=spot to identify cheaper nodes.

2. Step 2: Check node affinity syntax

   affinity: nodeAffinity: requiredDuringSchedulingIgnoredDuringExecution: nodeSelectorTerms: - matchExpressions: - key: "kubernetes.io/lifecycle" operator: In values: - spot correctly uses nodeAffinity with matchExpressions to select nodes labeled as spot.

3. Final Answer:

   affinity with nodeSelectorTerms matching lifecycle=spot label -> Option A

4. Quick Check:

   Spot instance selection uses nodeAffinity with lifecycle=spot label [OK]

Hint: Use nodeAffinity with lifecycle=spot label for spot nodes [OK]

Common Mistakes:

• Using nodeSelector with wrong label key
• Setting resource requests to 'spot' (invalid)
• Confusing tolerations with node affinity

3. Given this autoscaling configuration snippet for a Kubernetes deployment:

apiVersion: autoscaling/v2
kind: HorizontalPodAutoscaler
metadata:
  name: ml-model-hpa
spec:
  scaleTargetRef:
    apiVersion: apps/v1
    kind: Deployment
    name: ml-model
  minReplicas: 2
  maxReplicas: 10
  metrics:
  - type: Resource
    resource:
      name: cpu
      target:
        type: Utilization
        averageUtilization: 50

What happens when CPU usage rises to 75%?

medium

A. The number of pods will increase up to a maximum of 10

B. The number of pods will decrease to 2

C. The deployment will restart pods

D. Nothing changes because CPU target is 50%

Solution

1. Step 1: Understand Horizontal Pod Autoscaler (HPA) behavior

   HPA increases pods when CPU usage exceeds target utilization to balance load.

2. Step 2: Analyze CPU usage vs target

   CPU is at 75%, above the 50% target, so HPA will scale up pods up to maxReplicas (10).

3. Final Answer:

   The number of pods will increase up to a maximum of 10 -> Option A

4. Quick Check:

   CPU > target utilization triggers pod scaling up [OK]

Hint: CPU above target utilization triggers scaling up [OK]

Common Mistakes:

• Thinking pods scale down when CPU rises
• Confusing pod restart with scaling
• Assuming no change if CPU exceeds target

4. You have a cloud cost alert system but it keeps sending false alarms about overspending. What is the most likely cause?

medium

A. The cloud provider is charging incorrectly

B. The alert thresholds are set too low or too sensitive

C. The system is not connected to the billing API

D. The cost data is updated only once a year

Solution

1. Step 1: Understand alert system sensitivity

   Alerts trigger when costs exceed set thresholds; too low thresholds cause false alarms.

2. Step 2: Evaluate other options

   Incorrect charges or missing billing data cause different issues, not false alarms.

3. Final Answer:

   The alert thresholds are set too low or too sensitive -> Option B

4. Quick Check:

   Low alert thresholds cause false alarms [OK]

Hint: Check alert thresholds if false alarms occur [OK]

Common Mistakes:

• Blaming cloud provider without proof
• Ignoring alert configuration
• Assuming billing API is always connected

5. You want to reduce costs for a large ML training job that runs daily on cloud GPUs. Which combined strategy best optimizes cost at scale?

hard

A. Run training on CPUs to avoid GPU costs without changing code

B. Use only on-demand GPU instances and disable autoscaling

C. Use spot GPU instances with checkpointing and autoscaling to handle interruptions

D. Schedule training during peak hours to use full capacity

Solution

1. Step 1: Identify cost-saving options for GPU jobs

   Spot instances are cheaper but can be interrupted; checkpointing saves progress.

2. Step 2: Combine autoscaling with spot instances and checkpointing

   Autoscaling adjusts resources; checkpointing prevents data loss on interruptions.

3. Step 3: Evaluate other options

   On-demand is costly; CPUs are slower; peak hours usually cost more.

4. Final Answer:

   Use spot GPU instances with checkpointing and autoscaling to handle interruptions -> Option C

5. Quick Check:

   Spot + checkpoint + autoscale = best cost optimization [OK]

Hint: Combine spot instances with checkpointing and autoscaling [OK]

Common Mistakes:

• Ignoring interruptions on spot instances
• Using expensive on-demand only
• Running on CPUs without code changes
• Scheduling during costly peak hours