| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | 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 03:39:14 |
| Message-ID: | 0b1bd2e16eed5463c1dcb53c019a9bf37aace1c4.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 2021-08-31 at 18:55 -0700, Andres Freund wrote:
> > > 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.
>
> I think it's not helpful. Still increases the number of messages substantially in workloads
> with a lot of connections doing occasional queries. Which is common.
How come? If originally you send table statistics every 500ms, and now you send
table statistics and session statistics every second, that should amount to the
same thing. Where is my misunderstanding?
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2021-09-01 03:42:19 | Re: pgstat_send_connstats() introduces unnecessary timestamp and UDP overhead |
| Previous Message | Andres Freund | 2021-09-01 03:37:21 | Re: Replication slot drop message is sent after pgstats shutdown. |