Friday, February 7, 2020

[google-cloud-sql-discuss] Cloud SQL Tuning - SQL Server 2017 :: [ Response times are really high,CPU Usage is double for GKE + Cloud SQL (SQL SERVER 2017) ]

Hello,

Performance test with GCP GKE + Cloud SQL BETA (SQL Server 2017)

The response times in 400 user test for GKE + Cloud SQL are really high,CPU Usage is double.

  • We are seeing high Wait time for the Transaction log. ( we do write too much on disk )
  • We can not implement couple of option since we have limited control on instance

CloudSQL Configuration:

Cloud SQL configuration:

Database flags

optimize for ad hoc workloads  = on
agent xps = on
cost threshold for parallelism = 15

CPU

24

Memory

104 GB

N/W Throughput (MB/s)

2000 of 2000

Disk throughput (MB/s)

Read: 491.5 of 1,200.0
Write: 400.0 of 400.0

IOPS

Read: 25,000 of 25,000
Write: 25,000 of 25,000

JDBC Driver

7 (Compatible with SQL 2017)

CursorMethod

Select (Default)

Cardinality

130 ( Default with SQL 2017

 


To improve the response time and disk throughput, what are the best options to tune the Cloud SQL instance ??
and what are the upcoming feature enhancements in the general release ?

Please suggest the best configuration with database flags for optimal performance for CLOUD SQL (SQL SERVER 2017).



--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/4e2f6998-14cd-449c-a0d9-3f51e256da00%40googlegroups.com.

No comments:

Post a Comment