Topic 1 Question 20
You support an application deployed on Compute Engine. The application connects to a Cloud SQL instance to store and retrieve data. After an update to the application, users report errors showing database timeout messages. The number of concurrent active users remained stable. You need to find the most probable cause of the database timeout. What should you do?
Check the serial port logs of the Compute Engine instance.
Use Stackdriver Profiler to visualize the resources utilization throughout the application.
Determine whether there is an increased number of connections to the Cloud SQL instance.
Use Cloud Security Scanner to see whether your Cloud SQL is under a Distributed Denial of Service (DDoS) attack.
ユーザの投票
コメント(17)
Ans: B I don't find anything about ddos attacks and Cloud security Scanner & databases; its most used with App engine and compute so.
I go with Stackdriver profiler
👍 23francisco_guerra2021/06/20B - getting to know the app perf
👍 10ralf_cc2021/06/17Answer B: Use Stackdriver Profiler to visualize the resources utilization throughout the application.
High CPU usage can most definitely cause dropped or ignored connections. The database engine and underlying OS are fighting for resources and aren't able to respond to the connection in time. Finding out why the query is eating so much CPU usage and optimizing it. https://stackoverflow.com/questions/69919454/high-cpu-usage-on-cloud-sql-causing-timeouts
Cloud Profiler is a statistical, low-overhead profiler that continuously gathers CPU usage and memory-allocation information (supported profile types: CPU time, Heap, Allocated heap, Contention, Threads, Wall time) from your production applications. It attributes that information to the source code that generated it, helping you identify the parts of your application that are consuming the most resources, and otherwise illuminating your applications performance characteristics.
👍 5paul2233442022/04/15
シャッフルモード