From: Tom Lane <tgl@sss.pgh.pa.us>
To: Heikki Linnakangas <hlinnaka@iki.fi>
Cc: pgsql-hackers@postgreSQL.org
Subject: Re: Receive buffer size for the statistics socket
Date: Mon, 15 May 2017 10:07:08 -0400
Message-ID: <8899.1494857228@sss.pgh.pa.us> (raw)
In-Reply-To: <0a77466f-408d-ad7e-46c7-2efae718c4d3@iki.fi>
References: <22173.1494788088@sss.pgh.pa.us>
<0a77466f-408d-ad7e-46c7-2efae718c4d3@iki.fi>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
Heikki Linnakangas <hlinnaka@iki.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
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, hlinnaka@iki.fi
Subject: Re: Receive buffer size for the statistics socket
In-Reply-To: <8899.1494857228@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox