Why EC2 matters for compute in AWS - Performance Analysis

Time Complexity: Why EC2 matters for compute

O(n)

Understanding Time Complexity

When using EC2 for compute, it's important to know how the time to complete tasks grows as you add more work.

We want to understand how the number of EC2 operations changes as we increase the amount of computing needed.

Scenario Under Consideration

Analyze the time complexity of launching multiple EC2 instances to handle compute tasks.

// Launch multiple EC2 instances
for (int i = 0; i < n; i++) {
  ec2.runInstances({
    ImageId: 'ami-12345678',
    InstanceType: 't3.micro',
    MinCount: 1,
    MaxCount: 1
  });
}

This sequence launches n EC2 instances, each to handle a separate compute task.

Identify Repeating Operations

Look at what repeats as we increase n.

• Primary operation: The runInstances API call to start one EC2 instance.
• How many times: Exactly n times, once per instance.

How Execution Grows With Input

Each new compute task requires launching one EC2 instance, so the total API calls grow directly with the number of tasks.

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

Pattern observation: The number of operations increases in a straight line as tasks increase.

Final Time Complexity

Time Complexity: O(n)

This means the time or number of operations grows directly in proportion to the number of compute tasks.

Common Mistake

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

[OK] Correct: Each instance launch is a separate API call and takes time; more instances mean more calls and longer total time.

Interview Connect

Understanding how EC2 operations scale helps you design systems that handle growing workloads smoothly and shows you can think about real cloud costs and delays.

Self-Check

"What if we launched multiple EC2 instances in parallel using batch calls? How would the time complexity change?"