From: | Richard Lee <swift1984(at)gmail(dot)com> |
---|---|
To: | pryzby(at)telsasoft(dot)com |
Cc: | tomas(dot)vondra(at)2ndquadrant(dot)com, pgsql-performance(at)lists(dot)postgresql(dot)org |
Subject: | Re: Fwd: Query with high planning time compared to execution time |
Date: | 2018-11-06 11:40:50 |
Message-ID: | CALhvPTTfzo1xBirRFn+4NEAvGm9-VFBJF1SKvdHtyLM1NROmzA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Hi,
Ah, apologize for the mistake. The entire will take several hours to
complete and the problem query won't be executed until about halfway
through the benchmark. Should I do `perf record` when the query appears? Or
one `perf record` at the start of the test and another one when the query
appears? I imagine doing a `perf record` of the entire benchmark will fill
the storage (only about 100GB of space on the server).
Regards,
Richard Lee
On Mon, Nov 5, 2018 at 9:55 PM Justin Pryzby <pryzby(at)telsasoft(dot)com> wrote:
> On Mon, Nov 05, 2018 at 03:04:29PM +0800, Richard Lee wrote:
> > Executed perf-record and perf-report:
> > -bash-4.2$ perf record -g -- psql -U sri sri <
> > /var/lib/pgsql/10/data/pg_log/1-b10/query.txt
> > < ... snipped ... >
>
> That's showing perf output for the psql client. What you want is output
> for
> the server process (essentially all the client does is move data between
> the
> user to the server).
>
> https://wiki.postgresql.org/wiki/Profiling_with_perf
>
> Justin
>
From | Date | Subject | |
---|---|---|---|
Next Message | Lincoln Swaine-Moore | 2018-11-08 19:35:32 | NOT IN vs. NOT EXISTS performance |
Previous Message | Justin Pryzby | 2018-11-05 13:55:19 | Re: Fwd: Query with high planning time compared to execution time |