Re: pgstat_send_connstats() introduces unnecessary timestamp and UDP overhead

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, magnus(at)hagander(dot)net, pgsql-hackers(at)postgresql(dot)org
Subject: Re: pgstat_send_connstats() introduces unnecessary timestamp and UDP overhead
Date: 2021-09-01 01:33:15
Message-ID: YS7YWysXpG/sDUpu@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Aug 31, 2021 at 04:55:35AM +0200, Laurenz Albe wrote:
> In the view of that, how about doubling PGSTAT_STAT_INTERVAL to 1000
> milliseconds? That would mean slightly less up-to-date statistics, but
> I doubt that that will be a problem. And it should even out the increase
> in statistics messages, except in the case of lots of short-lived
> sessions. But in that scenario you cannot have session statistics
> without lots of extra messages, and such a workload has enough performance
> problems as it is, so I don't think we have to specifically worry about it.

Perhaps we could do that. Now, increasing an interval for the sake of
balancing the extra load created by a feature while impacting the
whole set of stats is not really appealing.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Mark Dilger 2021-09-01 01:41:51 Re: Delegating superuser tasks to new security roles (Was: Granting control of SUSET gucs to non-superusers)
Previous Message houzj.fnst@fujitsu.com 2021-09-01 01:28:38 RE: Added schema level support for publication.