Re: libpq compression

Поиск
Список
Период
Сортировка
От Peter Eisentraut
Тема Re: libpq compression
Дата
Msg-id 5c832f37-db91-edec-3b31-7caef365df69@enterprisedb.com
обсуждение исходный текст
Ответ на Re: libpq compression  (Andres Freund <andres@anarazel.de>)
Ответы Re: libpq compression
Re: libpq compression
Список pgsql-hackers
On 2020-11-02 20:50, Andres Freund wrote:
> On 2020-10-31 22:25:36 +0500, Andrey Borodin wrote:
>> But the price of compression is 1 cpu for 500MB/s (zstd). With a
>> 20Gbps network adapters cost of recompressing all traffic is at most
>> ~4 cores.
> 
> It's not quite that simple, because presumably each connection is going
> to be handled by one core at a time in the pooler. So it's easy to slow
> down peak throughput if you also have to deal with TLS etc.

Also, current deployments of connection poolers use rather small machine 
sizes.  Telling users you need 4 more cores per instance now to 
decompress and recompress all the traffic doesn't seem very attractive. 
Also, it's not unheard of to have more than one layer of connection 
pooling.  With that, this whole design sounds a bit like a 
heat-generation system. ;-)



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

Предыдущее
От: Peter Eisentraut
Дата:
Сообщение: Re: Move catalog toast table and index declarations
Следующее
От: Justin Pryzby
Дата:
Сообщение: list_free() in index_get_partition()