Cost optimization pillar in Azure - Time & Space Complexity

Time Complexity: Cost optimization pillar

O(n)

Understanding Time Complexity

We want to understand how the cost optimization steps in Azure grow as we add more resources or services.

How does the effort and operations needed change when scaling up cost-saving actions?

Scenario Under Consideration

Analyze the time complexity of this cost optimization process.

// Example: Checking and optimizing costs for multiple Azure resources
for (resource in resourceList) {
  checkCost(resource);
  if (costHigh(resource)) {
    applySavingsPlan(resource);
    resizeOrShutdown(resource);
  }
}

This sequence checks each resource's cost, then applies savings if needed.

Identify Repeating Operations

Look at what repeats as the number of resources grows.

• Primary operation: Checking cost and applying savings for each resource.
• How many times: Once per resource in the list.

How Execution Grows With Input

As you add more resources, the number of cost checks and savings actions grows directly with that number.

Input Size (n)	Approx. Api Calls/Operations
10	About 10 cost checks and possible savings actions
100	About 100 cost checks and possible savings actions
1000	About 1000 cost checks and possible savings actions

Pattern observation: The work grows evenly as you add more resources.

Final Time Complexity

Time Complexity: O(n)

This means the time to optimize costs grows in direct proportion to the number of resources.

Common Mistake

[X] Wrong: "Optimizing costs for many resources takes the same time as for one resource."

[OK] Correct: Each resource needs its own check and possible action, so time grows with the number of resources.

Interview Connect

Understanding how cost optimization scales helps you plan and explain cloud management clearly and confidently.

Self-Check

"What if we batch multiple resources together for cost checks? How would the time complexity change?"