Why GCP for cloud computing - Performance Analysis

Time Complexity: Why GCP for cloud computing

O(n)

Understanding Time Complexity

We want to understand how the time to complete tasks grows when using Google Cloud Platform (GCP) services.

How does adding more work affect the time GCP takes to respond?

Scenario Under Consideration

Analyze the time complexity of creating multiple virtual machines (VMs) in GCP.

// Create multiple Compute Engine instances
for (let i = 0; i < n; i++) {
  gcp.compute.instances.insert({
    project: 'my-project',
    zone: 'us-central1-a',
    resource: { name: `vm-instance-${i}`, machineType: 'zones/us-central1-a/machineTypes/n1-standard-1' }
  });
}
    

This code creates n virtual machines one by one in a specific zone.

Identify Repeating Operations

Look at what repeats as we create more VMs.

• Primary operation: API call to create one VM instance.
• How many times: Once per VM, so n times.

How Execution Grows With Input

Each VM creation takes one API call, so more VMs mean more calls.

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

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

Final Time Complexity

Time Complexity: O(n)

This means the time to create VMs grows in a straight line as you add more VMs.

Common Mistake

[X] Wrong: "Creating multiple VMs happens all at once, so time stays the same no matter how many VMs."

[OK] Correct: Each VM creation is a separate call that takes time, so more VMs mean more total time.

Interview Connect

Understanding how tasks scale in cloud platforms like GCP helps you design efficient systems and answer real-world questions confidently.

Self-Check

"What if we created all VMs using a batch API call instead of one by one? How would the time complexity change?"