Re: pgstat_send_connstats() introduces unnecessary timestamp and UDP overhead
От | Andres Freund |
---|---|
Тема | Re: pgstat_send_connstats() introduces unnecessary timestamp and UDP overhead |
Дата | |
Msg-id | 7FFBCABE-BB37-4919-AA3F-C74CDDCBB544@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 |
Hi, On August 31, 2021 6:33:15 PM PDT, Michael Paquier <michael@paquier.xyz> 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. 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. I think it's not helpful. Still increases the number of messages substantially in workloads with a lot of connections doingoccasional queries. Which is common. Andres -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
В списке pgsql-hackers по дате отправления: