VM states (running, stopped, deallocated) in Azure - Time & Space Complexity

Time Complexity: VM states (running, stopped, deallocated)

O(n)

Understanding Time Complexity

When managing virtual machines (VMs) in Azure, it is important to understand how the time to change VM states grows as you manage more VMs.

We want to know how the number of operations changes when starting, stopping, or deallocating multiple VMs.

Scenario Under Consideration

Analyze the time complexity of changing VM states in a loop.

for vm in vm_list:
    if vm.state == 'running':
        vm.stop()
    elif vm.state == 'stopped':
        vm.deallocate()
    elif vm.state == 'deallocated':
        vm.start()

# Each operation calls Azure API to change VM state
    

This code changes the state of each VM in a list by calling the appropriate Azure API.

Identify Repeating Operations

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

• Primary operation: Azure API call to change VM state (start, stop, deallocate)
• How many times: Once per VM in the list

How Execution Grows With Input

Each VM requires one API call to change its state, so the total calls grow directly with the number of VMs.

Input Size (n)	Approx. API Calls/Operations
10	10
100	100
1000	1000

Pattern observation: The number of API calls increases one-to-one with the number of VMs.

Final Time Complexity

Time Complexity: O(n)

This means the time to change VM states grows linearly as you add more VMs.

Common Mistake

[X] Wrong: "Changing the state of multiple VMs happens instantly regardless of how many VMs there are."

[OK] Correct: Each VM requires a separate API call, so more VMs mean more calls and more time.

Interview Connect

Understanding how operations scale with the number of resources helps you design efficient cloud management scripts and shows you think about real-world system behavior.

Self-Check

"What if we changed the code to batch start or stop multiple VMs in a single API call? How would the time complexity change?"