VM pricing models in Azure - Time & Space Complexity

Time Complexity: VM pricing models

O(n)

Understanding Time Complexity

We want to understand how the cost calculation effort grows when choosing different VM pricing models in Azure.

How does the number of VMs or pricing options affect the time to calculate total cost?

Scenario Under Consideration

Analyze the time complexity of calculating total cost for multiple VMs with different pricing models.

// Pseudocode for cost calculation
foreach vm in vmList {
  if vm.pricingModel == "PayAsYouGo" {
    cost += vm.hoursUsed * vm.hourlyRate;
  } else if vm.pricingModel == "Reserved" {
    cost += vm.reservedPrice;
  } else if vm.pricingModel == "Spot" {
    cost += vm.spotPrice * vm.hoursUsed;
  }
}
return cost;
    

This sequence calculates total cost by checking each VM's pricing model and applying the correct formula.

Identify Repeating Operations

Identify the API calls, resource provisioning, data transfers that repeat.

• Primary operation: Iterating over each VM to calculate cost based on pricing model.
• How many times: Once per VM in the list.

How Execution Grows With Input

As the number of VMs increases, the number of cost calculations grows proportionally.

Input Size (n)	Approx. Api Calls/Operations
10	10 cost calculations
100	100 cost calculations
1000	1000 cost calculations

Pattern observation: The work grows directly with the number of VMs.

Final Time Complexity

Time Complexity: O(n)

This means the time to calculate total cost grows linearly with the number of VMs.

Common Mistake

[X] Wrong: "Calculating cost for multiple VMs is constant time because pricing models are fixed."

[OK] Correct: Each VM requires a separate calculation, so more VMs mean more work.

Interview Connect

Understanding how cost calculations scale helps you design efficient billing tools and manage cloud budgets effectively.

Self-Check

"What if we grouped VMs by pricing model and calculated costs per group instead? How would the time complexity change?"