From: Rick Jones <rick.jones2@hp.com>
To: Ben Hutchings <bhutchings@solarflare.com>
Cc: mi wake <wakemi.wake@gmail.com>, netdev@vger.kernel.org
Subject: Re: rps testing questions
Date: Tue, 18 Jan 2011 11:10:36 -0800 [thread overview]
Message-ID: <4D35E5AC.6000804@hp.com> (raw)
In-Reply-To: <1295375676.3537.83.camel@bwh-desktop>
Ben Hutchings wrote:
> On Tue, 2011-01-18 at 10:23 -0800, Rick Jones wrote:
>
>>Ben Hutchings wrote:
>>
>>>On Mon, 2011-01-17 at 17:43 +0800, mi wake wrote:
>
> [...]
>
>>>>I do ab and tbench testing also find there is less tps with enable
>>>>rps.but,there is more cpu using when with enable rps.when with enable
>>>>rps ,softirqs is blanced on cpus.
>>>>
>>>>is there something wrong with my test?
>>>
>>>
>>>In addition to what Eric said, check the interrupt moderation settings
>>>(ethtool -c/-C options). One-way latency for a single request/response
>>>test will be at least the interrupt moderation value.
>>>
>>>I haven't tested RPS by itself (Solarflare NICs have plenty of hardware
>>>queues) so I don't know whether it can improve latency. However, RFS
>>>certainly does when there are many flows.
>>
>>Is there actually an expectation that either RPS or RFS would improve *latency*?
>> Multiple-stream throughput certainly, but with the additional work done to
>>spread things around, I wouldn't expect either to improve latency.
>
>
> Yes, it seems to make a big improvement to latency when many flows are
> active.
OK, you and I were using different definitions. I was speaking to single-stream
latency, but didn't say it explicitly (I may have subconsciously thought it was
implicit given the OP used a single instance of netperf :).
happy benchmarking,
rick jones
> Tom told me that one of his benchmarks was 200 * netperf TCP_RR
> in parallel, and I've seen over 40% reduction in latency for that. That
> said, allocating more RX queues might also help (sfc currently defaults
> to one per processor package rather than one per processor thread, due
> to concerns about CPU efficiency).
>
> Ben.
>
prev parent reply other threads:[~2011-01-18 19:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-17 9:43 rps testing questions mi wake
2011-01-17 9:53 ` Eric Dumazet
2011-01-18 8:34 ` mi wake
2011-01-17 13:08 ` Ben Hutchings
2011-01-18 18:23 ` Rick Jones
2011-01-18 18:34 ` Ben Hutchings
2011-01-18 19: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=4D35E5AC.6000804@hp.com \
--to=rick.jones2@hp.com \
--cc=bhutchings@solarflare.com \
--cc=netdev@vger.kernel.org \
--cc=wakemi.wake@gmail.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 NNTP newsgroup(s).