Re: [PERFORM] 9.4 -> 9.5 regression with queries through pgbouncer on RHEL 6

From: Andres Freund <andres(at)anarazel(dot)de>
To: Vladimir Borodin <root(at)simply(dot)name>
Cc: Антон Бушмелев <bushmelev(dot)aa(at)gmail(dot)com>, pgsql-performance(at)postgresql(dot)org, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PERFORM] 9.4 -> 9.5 regression with queries through pgbouncer on RHEL 6
Date: 2016-06-12 21:51:40
Message-ID: 20160612215140.znmnl4mpzvgxjmgn@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-performance

Hi Vladimir,

Thanks for these reports.

On 2016-06-13 00:42:19 +0300, Vladimir Borodin wrote:
> perf report -g -i pg9?_all.data >/tmp/pg9?_perf_report.txt

Any chance you could redo the reports with --no-children --call-graph=fractal
added? The mode that includes child overheads unfortunately makes the
output hard to interpet/compare.

> The results from pg9?_perf_report.txt are attached. Note that in all cases some events were lost, i.e.:
>
> root(at)pgload05g ~ # perf report -g -i pg94_all.data >/tmp/pg94_perf_report.txt
> Failed to open [vsyscall], continuing without symbols
> Warning:
> Processed 537137 events and lost 7846 chunks!

You can reduce the overhead by reducing the sampling frequency, e.g. by
specifying -F 300.

Greetings,

Andres Freund

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thom Brown 2016-06-13 00:53:48 Re: Confusing recovery message when target not hit
Previous Message Vladimir Borodin 2016-06-12 21:42:19 Re: [PERFORM] 9.4 -> 9.5 regression with queries through pgbouncer on RHEL 6

Browse pgsql-performance by date

  From Date Subject
Next Message Vladimir Borodin 2016-06-13 18:58:30 Re: [PERFORM] 9.4 -> 9.5 regression with queries through pgbouncer on RHEL 6
Previous Message Vladimir Borodin 2016-06-12 21:42:19 Re: [PERFORM] 9.4 -> 9.5 regression with queries through pgbouncer on RHEL 6