From: Mike Haertel <mike@ducky.net>
To: 9fans@cse.psu.edu
Subject: [9fans] having the Nagle cake and eating it too
Date: Mon, 26 Nov 2001 11:29:08 -0800 [thread overview]
Message-ID: <200111261929.fAQJT8f01844@ducky.net> (raw)
The problem with Nagle seems to be that it clobbers performance
of RPC applications. The communications pattern of such an
application is almost always:
write(...request...);
read(...response...);
(for clients) or
write(...response...)
read(...request...)
for servers.
Why not have read() force any outstanding writes to the network?
That way you could do the right thing even with programs whose
authors are too naive to know about turning off Nagle.
next reply other threads:[~2001-11-26 19:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-26 19:29 Mike Haertel [this message]
2001-11-27 10:18 ` Thomas Bushnell, BSG
2001-11-26 19:40 presotto
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=200111261929.fAQJT8f01844@ducky.net \
--to=mike@ducky.net \
--cc=9fans@cse.psu.edu \
/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).