Vitalii Tymchyshyn-2 wrote
> Well, I don't know anyone facing this problem with postgresql, but at tcp
> level data sending delays may indicate that Naggle's algorithm is in
> effect. See http://en.m.wikipedia.org/wiki/Nagle's_algorithm
Thanks for the information. I read through the Nagle's algorithm and
TCP_NODELAY concepts cursorily and my situation seems to be similar. i.e.
the machine which is having the issue seems to be sending ACK for every
request-response and not buffering it. This means that TCP_NODELAY seems to
be enabled (i.e. Nagle's algorithm disabled). But in the machine that is not
having issues, ACKs seem to be buffered. This means TCP_NODELAY is disabled
(i.e. Nagle's algorithm enabled). Am I right in this conslusion?
If so, how do I now disable TCP_NODELAY in hibernate/postgresql? There
doesn't seem to be much information on the internet about this.
--
View this message in context: http://postgresql.1045698.n5.nabble.com/Hibernate-over-postgresql-tp5806233p5806943.html
Sent from the PostgreSQL - jdbc mailing list archive at Nabble.com.