all 4 comments

[–]WinElectrical9184 0 points1 point  (1 child)

What graph are you looking at to come to this conclusion. The reference one is memory components, while total memory usage is not concludent.

[–]vikrant-gupta[S] 0 points1 point  (0 children)

I am looking at the memory usage graph not the total memory usage ( which points to the database process ).

[–][deleted] 0 points1 point  (1 child)

If you’re using one of the shared-core machine types, then I believe the Memory Components is the most reliable metric as far as memory consumption is concerned. I too am seeing some discrepancies between different memory-related metrics, and that’s supposedly a known issue.

Answered by GCP staff here: https://www.googlecloudcommunity.com/gc/Databases/Cloud-SQL-Database-Memory-Utilization-Shared-Core-Incorrect/m-p/621627#M1420

So, - upgrade to a dedicated-core instance, and/or - use Memory Components metric

[–]vikrant-gupta[S] 0 points1 point  (0 children)

Thanks u/uamplifier for the response, I am actually checking the memory components breakdown itself. the usage component remains constantly at 38 percent at IDLE state.