You support a consumer inventory application that runs on a multi-region instance of Cloud Spanner. A customer opened a support ticket to complain about slow response times. You notice a Cloud…

Question

Options

• AIncrease the number of processing units.
• BModify the database schema, and add additional indexes.
• CShard data required by the application into multiple instances.
• DDecrease the number of processing units.

• A
  76% (28)
• B
  8% (3)
• C
  14% (5)
• D
  3% (1)

Explanation

The first and most direct Google-recommended action for high CPU utilization in Cloud Spanner is to increase the number of processing units (or nodes). Cloud Spanner is designed to scale linearly by adding compute capacity, which immediately distributes the query load and reduces CPU pressure. This is the simplest and least disruptive first step. Modifying the schema and adding indexes (B) may help specific queries but requires analysis and testing - it is not the right first response to a general CPU saturation alert. Sharding data into multiple instances (C) is a complex architectural change, not a first step. Decreasing processing units (D) would worsen performance and is the opposite of what is needed.

No community discussion yet for this question.