Re: Receive buffer size for the statistics socket

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: Receive buffer size for the statistics socket
Date: 2017-05-15 14:07:08
Message-ID: 8899.1494857228@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Heikki Linnakangas <hlinnaka(at)iki(dot)fi> writes:
> On 05/14/2017 09:54 PM, Tom Lane wrote:
>> A further idea is that maybe backends should be tweaked to avoid
>> blasting large amounts of data at the stats collector in one go.
>> That would require more thought to design, though.

> The data is already sent in small < 1 kB messages, I don't see what more
> we can do in the sender side to avoid overwhelming the receiver. Except
> reduce the amount of data sent overall. But that only goes so far, we
> cannot eliminate the problem altogether, unless we also lose some detail.

I was wondering about some sort of rate-throttling on the messages.
For instance, stop after sending X kilobytes, leaving remaining counts
to be sent at the next opportunity. (Although it's not clear if you'd
ever catch up :-(.) Or just a short sleep after every X kilobytes, to
make it more probable that the stats collector gets to run and collect
the data.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Dilip Kumar 2017-05-15 14:21:59 Re: Increasing parallel workers at runtime
Previous Message Haribabu Kommi 2017-05-15 14:06:52 Increasing parallel workers at runtime