On 07/06/2015 04:30 PM, Tom Lane wrote:
Heikki Linnakangas <hlinn...@iki.fi> writes:
I was able to reproduce huge gains from this, after I introduced an
artificial latency to all network packets with:
tc qdisc add dev eth2 root netem delay 100ms
With that, and with the client on different host so that the traffic
goes through that high-latency network, I saw over 10x difference with
the same psql test you ran.
Committed, thanks!
Why does the committed patch do getsockopt() on server_fd rather than
port->sock? This seems at best confusing and at worst wrong.
Good catch, fixed!
- Heikki
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers