Cloud SQL pricing in GCP - Time & Space Complexity

Time Complexity: Cloud SQL pricing

O(n)

Understanding Time Complexity

We want to understand how the cost of using Cloud SQL changes as we use more resources.

How does adding more databases or increasing usage affect pricing?

Scenario Under Consideration

Analyze the pricing impact of creating multiple Cloud SQL instances and increasing their usage.

// Pseudocode for provisioning Cloud SQL instances and usage
for (int i = 0; i < n; i++) {
  createCloudSQLInstance(cpu=2, memory="8GB");
  runQueries(instanceId=i, queryCount=1000);
}

This sequence creates n Cloud SQL instances each with fixed CPU and memory, then runs a fixed number of queries on each.

Identify Repeating Operations

Look at what repeats as we increase n.

• Primary operation: Creating a Cloud SQL instance and running queries on it.
• How many times: Once per instance, so n times.

How Execution Grows With Input

Each new instance adds a fixed cost for CPU, memory, and storage, plus query processing costs.

Input Size (n)	Approx. Api Calls/Operations
10	10 instances created, 10,000 queries run
100	100 instances created, 100,000 queries run
1000	1000 instances created, 1,000,000 queries run

Cost grows directly with the number of instances and queries; doubling instances doubles cost.

Final Time Complexity

Time Complexity: O(n)

This means cost increases in a straight line as you add more Cloud SQL instances and usage.

Common Mistake

[X] Wrong: "Adding more instances won't increase cost much because queries are fixed."

[OK] Correct: Each instance adds fixed resource costs, so total cost grows with the number of instances, not just queries.

Interview Connect

Understanding how costs grow with resource usage helps you design scalable and budget-friendly cloud solutions.

Self-Check

"What if we increased the CPU and memory per instance instead of the number of instances? How would the time complexity change?"

Practice

1. Which factor does NOT directly affect the pricing of a Cloud SQL instance?

easy

A. The amount of network egress traffic

B. The amount of storage used

C. The size of the instance (CPU and RAM)

D. The number of users accessing the database

Solution

1. Step 1: Identify pricing factors for Cloud SQL

   Cloud SQL pricing depends on instance size, storage, backups, and network usage.

2. Step 2: Analyze the impact of users

   The number of users does not directly affect pricing; costs are based on resources used, not user count.

3. Final Answer:

   The number of users accessing the database -> Option D

4. Quick Check:

   Users do not affect pricing directly [OK]

Hint: Focus on resource usage, not user count, for pricing [OK]

Common Mistakes:

• Thinking more users always increase cost directly
• Confusing network traffic with user count
• Ignoring storage and instance size impact

2. Which of the following is the correct way to describe Cloud SQL pricing components?

easy

A. Pricing depends only on the number of database queries.

B. Pricing is fixed monthly regardless of usage.

C. Pricing is based on instance size, storage, backups, and network usage.

D. Pricing is based solely on the number of database users.

Solution

1. Step 1: Recall Cloud SQL pricing components

   Cloud SQL pricing includes instance size, storage, backups, and network usage.

2. Step 2: Compare options to pricing facts

   Only Pricing is based on instance size, storage, backups, and network usage. correctly lists the main pricing factors; others are incorrect or incomplete.

3. Final Answer:

   Pricing is based on instance size, storage, backups, and network usage. -> Option C

4. Quick Check:

   Pricing components = instance size, storage, backups, network [OK]

Hint: Remember pricing depends on resources, not fixed or query count [OK]

Common Mistakes:

• Assuming pricing is fixed monthly
• Confusing query count with pricing
• Ignoring backups and network costs

3. A Cloud SQL instance uses 4 vCPUs and 15 GB RAM, with 100 GB storage and 10 GB network egress. Which cost factor will likely be the highest contributor to the monthly bill?

medium

A. Instance size (CPU and RAM)

B. Storage

C. Network egress

D. Backups

Solution

1. Step 1: Analyze resource usage

   Instance size with 4 vCPUs and 15 GB RAM is a significant resource, usually costing more than storage or network for moderate usage.

2. Step 2: Compare other factors

   Storage of 100 GB and network egress of 10 GB are moderate; backups cost depends on backup size but usually less than instance size.

3. Final Answer:

   Instance size (CPU and RAM) -> Option A

4. Quick Check:

   Instance size usually costs most [OK]

Hint: Instance size usually dominates cost over storage and network [OK]

Common Mistakes:

• Overestimating network egress cost
• Ignoring instance size impact
• Assuming backups cost more than instance

4. You configured a Cloud SQL instance with 2 vCPUs and 7.5 GB RAM, but your monthly bill is unexpectedly high. Which of the following could be a likely cause?

medium

A. You set the instance size to 1 vCPU instead of 2.

B. You enabled automated backups with large backup storage.

C. You reduced network egress to zero.

D. You deleted all storage volumes.

Solution

1. Step 1: Identify possible cost causes

   Automated backups can increase storage costs significantly if backup size is large.

2. Step 2: Evaluate other options

   Setting instance size smaller reduces cost, reducing network egress lowers cost, deleting storage is not possible without data loss and would not increase cost.

3. Final Answer:

   You enabled automated backups with large backup storage. -> Option B

4. Quick Check:

   Backups can increase cost unexpectedly [OK]

Hint: Check backup storage size if bill is high unexpectedly [OK]

Common Mistakes:

• Assuming smaller instance size increases cost
• Ignoring backup storage impact
• Thinking deleting storage increases cost

5. You want to minimize your Cloud SQL monthly cost while maintaining performance. Which combination of actions is best?

hard

A. Choose an appropriate instance size, use balanced storage type, and schedule backups during off-peak hours.

B. Choose a larger instance size, use HDD storage, and disable backups.

C. Choose the smallest instance size, disable backups, and ignore network usage.

D. Choose a smaller instance size, use SSD storage, and enable automated backups.

Solution

1. Step 1: Balance instance size and storage

   Choosing an appropriate instance size and balanced storage optimizes cost and performance.

2. Step 2: Manage backups smartly

   Scheduling backups during off-peak hours reduces performance impact and controls costs without disabling backups.

3. Final Answer:

   Choose an appropriate instance size, use balanced storage type, and schedule backups during off-peak hours. -> Option A

4. Quick Check:

   Balance resources and backup timing for cost and performance [OK]

Hint: Balance size, storage, and backup timing for best cost [OK]

Common Mistakes:

• Choosing smallest instance ignoring performance
• Disabling backups risking data loss
• Ignoring storage type impact