Re: pgstat_send_connstats() introduces unnecessary timestamp and UDP overhead
От | Andres Freund |
---|---|
Тема | Re: pgstat_send_connstats() introduces unnecessary timestamp and UDP overhead |
Дата | |
Msg-id | 20210901041625.jhlaqkutf3gdau4z@alap3.anarazel.de обсуждение исходный текст |
Ответ на | Re: pgstat_send_connstats() introduces unnecessary timestamp and UDP overhead (Laurenz Albe <laurenz.albe@cybertec.at>) |
Ответы |
Re: pgstat_send_connstats() introduces unnecessary timestamp and UDP overhead
|
Список | pgsql-hackers |
On 2021-09-01 05:39:14 +0200, Laurenz Albe wrote: > 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_INTERVALto 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? Consider the case of one query a second.
В списке pgsql-hackers по дате отправления: