From: Eicke Friedrich <tady@gmx.net>
To: bridge@lists.osdl.org
Subject: [Bridge] bridge latency
Date: Sun, 16 May 2004 10:49:18 +0200 [thread overview]
Message-ID: <40A72B0E.20104@gmx.net> (raw)
Hi list,
we did an investigation of a firewalling Linux bridge in terms of
latency and throughput using DAG 3.5E interfaces for precise
timestamping of ip packets [1]. The overall results are very good but
one fact we can't explain. The following URL points to an image of
such an measuring where we push 60MBits/s TCP traffic through the
bridge in one direction:
http://kea.informatik.uni-leipzig.de/ipp2p/delay/color_60e_plain_out.png
If you look at the image you'll see the max line showing regular (one
per minute) spikes. I've absolutly no idea where these spikes may come
from. So I want to ask you, if you could imagine a reason for these
spikes? These are only few packets but for us it's important to find
out why they get sometimes delayed this much longer.
Some background about the bridging box:
Hardware:
Pentium4 1.7GHz, 1.024MB RAM, 2 x 3Com 3c905 [Boomerang] being br0,
3Com 3c905B as management interface.
Software:
vanilla Linux Kernel 2.6.3 with patched in CONNMARK extension, STP was
disabled
Other:
The bridge was running in plain mode wich means no other modules like
iptables, ebtables or packet scheduler were loaded. It was running in
runlevel 3, multiuser networking without x-system.
For comparison only this link shows what happens if we push as much
TCP traffic in one direction (~97.5 MBits/s) through the bridge having
iptables loaded:
http://kea.informatik.uni-leipzig.de/ipp2p/delay/color_max_ipp2p_120c_delay-0.png
Thanks in advance for any comments or suggestions!
Cheers,
Eicke
[1] Endace Measurement Systems: http://www.endace.com/
next reply other threads:[~2004-05-16 8:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-16 8:49 Eicke Friedrich [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-05-17 8:25 [Bridge] bridge latency Eicke Friedrich
2004-05-17 15:47 ` Stephen Hemminger
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=40A72B0E.20104@gmx.net \
--to=tady@gmx.net \
--cc=bridge@lists.osdl.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