Re: Google Query Insights ?!

It's the default graph that the query insights dashboard displays.\ The point of showing vCPU is to compare to the CPU (and waits) so if CPU load is at at different scale it is sort of pointless/misleading to show the vCPU at a different scale.
Quite confusing to me.
Was on a call with company who was adding column to a postgres table. Usually it's almost instant. In this case it was running for 24 hours. We looked at Query insights an nothing going on. Looked at pg_stat_activity and could see right away it was waiting on a lock held by vacuum. (both explain the problem and raising some concerns on why vacuum is running so long)

On Thu, Jan 26, 2023 at 4:14 PM Graham Wood <graham_wood_at_yahoo.com> wrote:

> Looks to me like one axis is used for the CPU capacity (always 6), and the
> other for the CPU used. Is this graph generated with a query?
>
> Cheers, Graham
>
> Sent from my iPhone
>
> On Jan 26, 2023, at 9:27 AM, kyle Hailey <kylelf_at_gmail.com> wrote:
>
> 
>
> Anyone use Google Query Insights? I can't figure why the main graph has
> dual axis or what they are and how they would relate:
>
> The dual axis have no labels. The flyover CPU value says CPU is 0.05 and
> yet the green, the CPU, in chart goes over 6?! and that axis goes from not
> from 0-7 but starts at 5 and goes to 7. Oh and there is a second y axis on
> right that goes 0 - 0.1 ( this is Query Insights )
>
> <image.png>
>
>

--
http://www.freelists.org/webpage/oracle-l