Re: More efficient truncation of pg_stat_activity query strings

From: Andres Freund <andres(at)anarazel(dot)de>
To: Kuntal Ghosh <kuntalghosh(dot)2007(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: More efficient truncation of pg_stat_activity query strings
Date: 2017-09-19 18:49:18
Message-ID: 20170919184918.lmvh7xhkvxkpvshz@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On 2017-09-15 17:43:35 +0530, Kuntal Ghosh wrote:
> The patch looks good to me. I've done some regression testing with a
> custom script on my local system. The script contains the following
> statement:

> SELECT 'aaa..<repeated 600 times>' as col;
>
> Test 1
> -----------------------------------
> duration: 300 seconds
> clients/threads: 1

> With the patch TPS:13628 (+3.39%)
> + 0.36% 0.21% postgres postgres [.] pgstat_report_activity
>
> Test 2
> -----------------------------------
> duration: 300 seconds
> clients/threads: 8

> With the patch TPS: 63949 (+20.4%)
> + 0.40% 0.25% postgres postgres [.] pgstat_report_activity
>
> This shows the significance of this patch in terms of performance
> improvement of pgstat_report_activity. Is there any other tests I
> should do for the same?

Thanks for the test! I think this looks good, no further tests
necessary.

Greetings,

Andres Freund

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Merlin Moncure 2017-09-19 18:49:56 Re: PoC plpgsql - possibility to force custom or generic plan
Previous Message Andrew Dunstan 2017-09-19 18:47:26 Re: Re: [COMMITTERS] pgsql: Add citext_pattern_ops for citext contrib module