Friday, February 7, 2020

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

Hi Kenny,

Cloud SQL cannot achieve the same performance as a well-tuned traditional configuration, which may have local disks, dedicated DB hardware/vms, or zero latency to application servers. I should also note that, Cloud SQL does not support SUPER privileges for security reasons. However, Cloud SQL provides you with a fully Google managed, integrated and reliable database. If you require more access and control, you may either run and configure your database on a Cloud Compute Engine VM or select other storage options as per your usecase. 

In order to decrease the latency and improve the disk throughput, You may check the location of the writer and database. Sending data a long distance will introduce latency, and larger disks and upgrading your machine type have more IOPS available. I also recommend to take a look at the best practices for getting the best performance from Cloud SQL.  I would like to add that, for getting the optimal performance, it is important to run tests and measure.

We don't have any roadmap on public, but you may consistently check the release note for production updates.

--
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/47dd5074-5616-47af-bfad-3bbd576b972e%40googlegroups.com.

No comments:

Post a Comment