Re: Command statistics system (cmdstats) - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Command statistics system (cmdstats)
Date
Msg-id 20200917045123.GG2873@paquier.xyz
Whole thread Raw
In response to Re: Command statistics system (cmdstats)  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Command statistics system (cmdstats)  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
On Wed, Jun 10, 2020 at 01:45:02PM -0400, Robert Haas wrote:
> My spidey sense is tingling here, telling me that we need some actual
> benchmarking. Like, suppose we test the two patches under normal cases
> and under cases that are constructed to be as bad as possible for each
> of them. Or suppose we test this patch with the lock mitigation
> strategies and then remove the mitigations for some inexpensive
> command (e.g. SHOW) and then use pgbench to spam that command. Like
> you, I suspect that the locking mitigations are important in some
> workloads, but it would be good to have some figures to back that out,
> as well as to find out whether there's still too much overhead.

This patch has not received any replies after this comment for three
months, so I am marking it as returned with feedback.  I agree that
this should be benchmarked carefully.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Is it useful to record whether plans are generic or custom?
Next
From: Michael Paquier
Date:
Subject: Re: New SQL counter statistics view (pg_stat_sql)