From: Chris Wilson <chris@netservers.co.uk>
To: tsh@mrc-lmb.cam.ac.uk
Cc: netfilter@lists.netfilter.org
Subject: Re: Interesting problems
Date: Tue, 5 Aug 2003 12:00:37 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.44.0308051156060.21531-100000@localhost> (raw)
In-Reply-To: <200308051034.LAA447988@alf1.lmb.internal>
Hi Terry,
> Chris, I'm interested in why your 50 users generate 3000 connections.
We have a number of customers' servers hosted here, about 40 boxes. There
are probably about 30-40 desktop users as well, and one customer with
maybe 10 servers of his own. Probably the servers are responsible for most
of the connections, but I don't have an actual breakdown.
> I realise that different iptables activities will present different
> cpu loads (packet rate, number of entries in the tables, number of
> active connections etc) but do you have any feel for which of these
> is the most costly?
I think searching the connections table is the most costly thing. The
Slammer worm brought some of our firewalls to their knees with IRQ load
(crappy Realtek network cards) and connection lookups. Reducing the number
of conntracks from 65,000 to 4096 made the systems usable again. But
that's just my own experience, I suspect that the real Netfilter
developers have a much better idea than me where the bottlenecks are.
Cheers, Chris.
--
___ __ _
/ __// / ,__(_)_ | Chris Wilson -- UNIX Firewall Lead Developer |
/ (_ / ,\/ _/ /_ \ | NetServers.co.uk http://www.netservers.co.uk |
\ _//_/_/_//_/___/ | 21 Signet Court, Cambridge, UK. 01223 576516 |
next prev parent reply other threads:[~2003-08-05 11:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-04 20:41 Interesting problems Peteris Krumins
2003-08-05 9:38 ` Chris Wilson
2003-08-05 10:34 ` tsh
2003-08-05 11:00 ` Chris Wilson [this message]
2003-08-05 19:54 ` Re[2]: " Peteris Krumins
2003-08-06 10:03 ` Chris Wilson
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=Pine.LNX.4.44.0308051156060.21531-100000@localhost \
--to=chris@netservers.co.uk \
--cc=netfilter@lists.netfilter.org \
--cc=tsh@mrc-lmb.cam.ac.uk \
/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