Re: Proposal: PqSendBuffer removal

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Proposal: PqSendBuffer removal
Дата
Msg-id 14283.1583449481@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: Proposal: PqSendBuffer removal  (Aleksei Ivanov <iv.alekseii@gmail.com>)
Ответы Re: Proposal: PqSendBuffer removal  (Aleksei Ivanov <iv.alekseii@gmail.com>)
Список pgsql-hackers
Aleksei Ivanov <iv.alekseii@gmail.com> writes:
> Yes, you are right there will be a separate call to send the data, but is
> copying data each time more costly operation than just one syscall?

What do you mean "just one syscall"?  The entire point here is that it'd
take more syscalls to send the same amount of data.

It does strike me that with the v3 protocol, we do sometimes have cases
where internal_putbytes is reached with a fairly large "len".  If we've
flushed out what's in PqSendBuffer to start with, and there's more than
a bufferload remaining in the source data, we could send the source
data directly to output without copying it to the buffer first.
That could actually result in *fewer* kernel calls not more, if "len"
is large enough.  But I strongly doubt that a code path that nets
out to more kernel calls will win.

            regards, tom lane



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Fabien COELHO
Дата:
Сообщение: Re: pgbench: option delaying queries till connectionsestablishment?
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Allowing ALTER TYPE to change storage strategy