From: "Adam McLaurin" <lkml@irotas.net>
To: linux-kernel@vger.kernel.org
Subject: Loopback and Nagle's algorithm
Date: Mon, 11 Apr 2011 22:37:49 -0400 [thread overview]
Message-ID: <1302575869.13492.1440076201@webmail.messagingengine.com> (raw)
I understand that disabling Nagle's algorithm via TCP_NODELAY will
generally degrade throughput. However, in my scenario (150 byte
messages, sending as fast as possible), the actual throughput penalty
over the network is marginal (maybe 10% at most).
However, when I disable Nagle's algorithm when connecting over loopback,
the performance hit is *huge* - 10x reduction in throughput.
The question is, why is disabling Nagle's algorithm on loopback so much
worse w.r.t. throughput? Is there anything I can do to reduce the
incurred throughput penalty?
Thanks,
Adam
next reply other threads:[~2011-04-12 2:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-12 2:37 Adam McLaurin [this message]
2011-04-12 9:42 ` Loopback and Nagle's algorithm Alejandro Riveira Fernández
2011-04-12 9:45 ` Will Newton
2011-04-12 11:04 ` Adam McLaurin
2011-04-12 11:54 ` Jiri Kosina
2011-04-12 13:08 ` Eric Dumazet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1302575869.13492.1440076201@webmail.messagingengine.com \
--to=lkml@irotas.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.