From: Rick Jones <rick.jones2@hp.com>
To: "H.K. Jerry Chu" <hkjerry.chu@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: First pass at MSG_FASTOPEN support in top-of-trunk netperf
Date: Tue, 28 Aug 2012 10:10:30 -0700 [thread overview]
Message-ID: <503CFB86.2020008@hp.com> (raw)
In-Reply-To: <CAFbMe2MY11VoXbGPDcLzHiHBzskoQk6eL1S9VWV5Vd1u0aRjNw@mail.gmail.com>
>> There was a ~25% increase in TCP_CRR performance, even without the server
>> actually accepting the magic TCP option. Is that actually expected?
>
> I have a locally enhanced netperf for TCP_CRR over Fast Open and I've
> noticed the numbers can change drastically between runs. I have not got
> the time to investigate why. (Does it have to do with scheduler and CPU
> locality?) How consistent is your perf number?
I recall the performance being reasonably consistent but there has been
a vacation of my own in the middle there so my dimm memory is a bit fuzzy :)
Historically (and going beyond just Linux) a TCP_CRR test can have some
non-trivial run to run variation thanks to (attempted) TIME_WAIT reuse.
Whether that is happening to you I don't know, but it might be worth a
look.
> I plan to submit the server side code soon and will work with you to add
> the server side support to TCP_CRR (it requires a new TCP_FASTOPEN
> socket option to enable Fast Open on a listener.)
Works for me.
happy benchmarking,
rick jones
prev parent reply other threads:[~2012-08-28 17:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-07 1:47 First pass at MSG_FASTOPEN support in top-of-trunk netperf Rick Jones
2012-08-23 14:15 ` H.K. Jerry Chu
2012-08-28 17:10 ` Rick Jones [this message]
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=503CFB86.2020008@hp.com \
--to=rick.jones2@hp.com \
--cc=hkjerry.chu@gmail.com \
--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).