On Thursday, 31 December 2015 at 12:09:30 UTC, Etienne Cimon
wrote:
That would be the other way around. TCP_NODELAY is not enabled
in the local connection, which makes a ~20-30ms difference per
request on keep-alive connections and is the bottleneck in this
case. Enabling it makes the library competitive in these
benchmarks.
I don't know how the benchmarks are set up, but I would assume
that they don't use a local socket. I wonder if they run the
database on the same machine, maybe they do, but that's not
realistic, so they really should not.
