From: Evgeni Gechev <etg@setcom.bg>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Bandwith limitation
Date: Mon, 10 Mar 2003 18:42:06 +0000 [thread overview]
Message-ID: <marc-lartc-104732183116776@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104728577309146@msgid-missing>
Stef Coene wrote:
> > Stef,
> >
> > We have about 3200 iptables rules on our bridge. I've tested today to
> > remove 1000 of these rules. The load dropped from about 40% to 25%. So I
> > think the iptables rule take up the most of the CPU load. Do you think this
> > is a problem of ineffeciency of iptables or just a 'limitation' in the
> > TCP/IP stack of linux ?
> I don't think it's a limitation. I think you reached the point where you need
> a bigger machine :)
Some topic-related observations:
AMD Athlon XP1700+ (1466), 4xRealtek8139, 5-6Mbit/s - nearly reaching the limit
of machine capabalities
P4 2000, 3com905C+BROADCOM BCM5701, 40-50Mbit/s - far better behavior
Same configuration on both, thousands of iptables rules, and on the p4 machine
there are 200-250 concurrent pppoe sessions (none on the athlon)
>
> Maybe you can try to iptables mailing list to find more info about the
> performance you can expect :
> http://lists.netfilter.org/mailman/listinfo/netfilter
>
> Stef
>
> --
>
> stef.coene@docum.org
> "Using Linux as bandwidth manager"
> http://www.docum.org/
> #lartc @ irc.oftc.net
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-03-10 18:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-10 8:41 [LARTC] Bandwith limitation Rinse Kloek
2003-03-10 17:41 ` Stef Coene
2003-03-10 17:50 ` Rinse Kloek
2003-03-10 18:00 ` Stef Coene
2003-03-10 18:42 ` Evgeni Gechev [this message]
2003-03-10 19:03 ` Raúl Alexis Betancort Santana
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=marc-lartc-104732183116776@msgid-missing \
--to=etg@setcom.bg \
--cc=lartc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.