Spanner pitr load testing

Before topology service is ready for GA we need to determine the baseline and under load performance of the spanner database to ensure configuration is appropriate.

Objectives

• Test performance impact of Point-in-Time Recovery (PITR) configuration
• Pre-load database with ~35M claims using production schema and Run baseline tests: 500 writes/sec and 43k reads/sec
• Document production-ready performance baselines for our instance configuration
• Observe the performance limitations by increasing concurrency until there is contention so we know where to put our alert thresholds - GCP recommends 65% CPU
• Resolve high-latency issues with Google Cloud Support

Testing project https://gitlab.com/daveyleach/spanner_load_test

source