On Mon, Mar 26, 2018 at 7:51 PM, Craig Ringer <craig@2ndquadrant.com> wrote:
> There's been no visible consideration of overheads and comparison with
> existing v3 protocol. Personally I'm fine with adding some protocol overhead
> in bytes terms; low latency links have the bandwidth not to care much
> compared to payload sizes etc. On high latency links it's all about the
> round trips, not message sizes. But I want to know what those overheads are,
> and why they're there.
I think that the overhead of any new protocol (or protocol version)
ought to be a major consideration. Overhead includes, but is not
limited to, number of bytes sent over the wire. It also includes how
fast we can parse that protocol; Andres's earlier comments on this
thread abut Parse/Bind/Execute being slower than Query are on point.
If we implement a new protocol, we should measure how many QPS we can
push through it (for both prepared and unprepared queries).
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company