Re: Add min and max execute statement time in pg_stat_statement - Mailing list pgsql-hackers

From Mitsumasa KONDO
Subject Re: Add min and max execute statement time in pg_stat_statement
Date
Msg-id CADupcHUfkPWfBzLPAxnnciuu1fCnNe1OnZ8kDkEdVUpMrJFCQg@mail.gmail.com
Whole thread Raw
In response to Re: Add min and max execute statement time in pg_stat_statement  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: Add min and max execute statement time in pg_stat_statement  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
2014-01-27 Andrew Dunstan <andrew@dunslane.net>

On 01/27/2014 07:09 AM, KONDO Mitsumasa wrote:
(2014/01/23 23:18), Andrew Dunstan wrote:
What is more, if the square root calculation is affecting your benchmarks, I
suspect you are benchmarking the wrong thing.
I run another test that has two pgbench-clients in same time, one is select-only-query and another is executing 'SELECT *  pg_stat_statement' query in every one second. I used v6 patch in this test.



The issue of concern is not the performance of pg_stat_statements, AUIU. The issue is whether this patch affects performance generally, i.e. is there a significant cost in collecting these extra stats. To test this you would compare two general pgbench runs, one with the patch applied and one without.
I showed first test result which is compared with without pg_stat_statements and without patch last day.  They ran in same server and same benchmark settings(clients and scale factor) as today's result. When you merge and see the results, you can confirm not to affect of performance in my patch.

Regards,
--
Mitsumasa KONDO
NTT Open Source Software Center

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Changeset Extraction v7.1
Next
From: Robert Haas
Date:
Subject: Re: What is happening on buildfarm member crake?