From: Stephen Hemminger <shemminger@vyatta.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Kernel forwarding performance test regressions
Date: Wed, 19 Aug 2009 11:00:10 -0700 [thread overview]
Message-ID: <20090819110010.53b630cd@nehalam> (raw)
Vyatta regularly runs RFC2544 performance tests as part of
the QA release regression tests. These tests are run using
a Spirent analyzer that sends packets at maximum rate and
measures the number of packets received.
The interesting (worst case) number is the forwarding percentage for
minimum size Ethernet packets. For packets 1K and above all the packets
get through but for smaller sizes the system can't keep up.
The hardware is Dell based
CPU is Intel Dual Core E2220 @ 2.40GHz (or 2.2GHz)
NIC's are internal Broadcom (tg3).
Size 2.6.23 2.6.24 2.6.26 2.6.29 2.6.30
64 14.% 20% 21% 17% 19%
128 22 33 34 28 32
256 37 52 58 49 54
512 67 85 83 85 85
1024 100 100 100 100 100
1280 100 100 100 100 100
1518 100 100 100 100 100
Some other details:
* Hardware change between 2.6.24 -> 2.6.26 numbers
went from 2.2 to 2.4Ghz
* no SMP affinity (or irqbalance) is done,
numbers are significantly better if IRQ's are pinned.
2.6.26 goes from 20% to 32%
* unidirectional numbers are 2X the bidirectional numbers:
2.6.26 goes from 20% to 40%
* this is single stream (doesn't help/use multiqueue)
* system loads iptables but does not use it, so each packet
sees the overhead of null rules.
So kernel 2.6.29 had an observable dip in performance
which seems to be mostly recovered in 2.6.30.
These are from our QA, not me so please don't ask me for
"please rerun with XX enabled", go run the same test
yourself with pktgen.
--
next reply other threads:[~2009-08-19 18:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-19 18:00 Stephen Hemminger [this message]
2009-08-25 9:47 ` Kernel forwarding performance test regressions Eric Dumazet
2009-08-25 16:04 ` Stephen Hemminger
2009-08-25 16:25 ` 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=20090819110010.53b630cd@nehalam \
--to=shemminger@vyatta.com \
--cc=davem@davemloft.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).