From: "Alejandro Riveira Fernández" <ariveira@gmail.com>
To: "Adam McLaurin" <lkml@irotas.net>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: Loopback and Nagle's algorithm
Date: Tue, 12 Apr 2011 11:42:10 +0200 [thread overview]
Message-ID: <20110412114210.65f202cc@varda> (raw)
In-Reply-To: <1302575869.13492.1440076201@webmail.messagingengine.com>
El Mon, 11 Apr 2011 22:37:49 -0400
"Adam McLaurin" <lkml@irotas.net> escribió:
Just CCing netdev
> 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
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next parent reply other threads:[~2011-04-12 9:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1302575869.13492.1440076201@webmail.messagingengine.com>
2011-04-12 9:42 ` Alejandro Riveira Fernández [this message]
[not found] ` <BANLkTi=jpdLRc35DkBhLmUr8-P+ggcrgoA@mail.gmail.com>
[not found] ` <1302606246.21782.1440195277@webmail.messagingengine.com>
[not found] ` <alpine.LRH.2.00.1104121354010.6953@twin.jikos.cz>
2011-04-12 13:08 ` Loopback and Nagle's algorithm 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=20110412114210.65f202cc@varda \
--to=ariveira@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@irotas.net \
--cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).