Skip to main content
Skip table of contents

Cloud Spanner Cloud Instance

Cloud Spanner1.png

The Cloud Spanner tab

The Cloud Spanner instance has the following properties:

Name

Instance name.

Configuration

Regional or Multi-Region Spanner instance.

Processing Units

Number of processing units.

Nodes

Number of nodes.

Storage Utilization

Amount of storage for the instance to use.

Backup

Amount of storage for the instance to use for backups in GiB.

Region

Region the instance was assigned to.

Committed Usage

Commitment setting for the instance. Longer commitments lower the price.

Databases

Total number of sources to be migrated into the cloud.

Instance Group Name

Name of the instance group the instance is associated with.

Add Instance

To add a Cloud Spanner cloud instance:

  1. In the Cloud Spanner tab, press the Create button.

  2. In the Choose databases to migrate panel, select the sources to migrate to the cloud instance.

  3. In the Cloud Instance Information panel, specify:

    • Instance Group

    • Instance Name

    • Target Platform: GCP Cloud Spanner.

    • Configuration: Regional or Multi-Region.

    • Compute Unit: Processing Units or Nodes.

    • Region

    • Committed Usage

    • Storage Utilization. Calculated automatically based on the cumulative size of the sources selected, with a percentage padding to allow for growth and operation.

    • Backup

  4. Press the Confirm button to save the configuration, or the Cancel button to discard it.

Cloud Spanner.png

The Instance Configuration dialog

Compute Unit and Sizing

Cloud Spanner has characteristics and limits that affect the Processing Units or Nodes count settings.

The initial value is automatically calculated and assigned in an attempt to adhere to the following limits:

  • Maximum database storage allowed per node of 4 TiB.

  • Maximum number of databases allowed per node of 100.

  • Maximum read operations per second allowed per node of 10K ops/sec (14K if multi-region).

  • Maximum write operations per second allowed per node of 2K ops /sec (1.8K if multi-region).

  • Region-specific maximum node count per project.

To accommodate real-world operational scenarios, additional resources are allocated to the underlying required resources to allow natural growth and spike usage.

mMC collects the data sizes and various object counts during the source scanning.

Workload data is collected from AWR reports in Oracle, and via Extended Scan mode in mMC for other database engine types.

Attempting to under-provision the target instance concerning the sources selected to migrate into it produces an error. 

For external documentation related to sizing and limitations, see:

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.

Contact Support Close