From: ht@inf.ed.ac.uk (Henry S. Thompson)
To: cygwin@cygwin.com
Subject: Re: socket performance
Date: Tue, 10 Jan 2012 07:22:00 -0000 [thread overview]
Message-ID: <f5bobucggxs.fsf@calexico.inf.ed.ac.uk> (raw)
In-Reply-To: <20120109134311.GH15470@calimero.vinschen.de> (Corinna Vinschen's message of "Mon, 9 Jan 2012 14:43:11 +0100")
Corinna Vinschen writes:
> it's nice to know that you could increase the performance by increasing
> the buffer sizes. However, I'm reluctant to implement this as a generic
> option. As far as I know the socket buffers are taken from nonpaged pool,
> so generically using 2 Meg buffers will take a lot of precious resources.
And contribute to bufferbloat problems [1] [2] elsewhere!
ht
[1] http://queue.acm.org/detail.cfm?id=2076798
[2] http://queue.acm.org/detail.cfm?id=2071893
--
Henry S. Thompson, School of Informatics, University of Edinburgh
10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
Fax: (44) 131 650-4587, e-mail: ht@inf.ed.ac.uk
URL: http://www.ltg.ed.ac.uk/~ht/
[mail from me _always_ has a .sig like this -- mail without it is forged spam]
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2012-01-10 7:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-04 13:49 Building cygwin1.dll Johan van den Berg
2012-01-04 14:25 ` marco atzeri
2012-01-04 19:26 ` Johan van den Berg
2012-01-09 13:44 ` socket performance (was Re: Building cygwin1.dll) Corinna Vinschen
2012-01-09 16:37 ` Václav Zeman
2012-01-10 8:46 ` Corinna Vinschen
2012-01-10 7:22 ` Henry S. Thompson [this message]
2012-01-10 7:53 ` socket performance Daniel Colascione
2012-01-10 12:46 ` socket performance (was Re: Building cygwin1.dll) Johan van den Berg
2012-01-10 14:46 ` Corinna Vinschen
2012-01-10 15:25 ` Steven Hartland
2012-01-10 16:28 ` Corinna Vinschen
2012-01-10 16:39 ` Corinna Vinschen
2012-01-10 17:05 ` Steven Hartland
2012-01-10 17:27 ` Corinna Vinschen
2012-01-10 18:23 ` Steven Hartland
2012-01-11 14:05 ` Corinna Vinschen
2012-01-11 14:20 ` Carson Chittom
2012-01-11 14:43 ` Corinna Vinschen
2012-01-11 6:25 ` Johan van den Berg
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=f5bobucggxs.fsf@calexico.inf.ed.ac.uk \
--to=ht@inf.ed.ac.uk \
--cc=cygwin@cygwin.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).