All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sertys <sertys@supportivo.org>
To: Netfilter list <netfilter@lists.netfilter.org>
Subject: Re: iptables on multiple CPUs (SMP & Hyperthreading question)
Date: Fri, 3 Jun 2005 12:12:08 +0000 (UTC)
Date: Sat, 04 Jun 2005 21:29:49 +0300	[thread overview]
Message-ID: <opsruyzzkd76nf2y@xonix> (raw)
In-Reply-To: <429FBD3B.4040007@gmx.co.uk>

On Thu, 02 Jun 2005 21:15:23 -0500, /dev/rob0 <rob0@gmx.co.uk> wrote:

> Michael Buffer wrote:
>> I'm considering purchasing some firewall machines for my organization,  
>> and
>> I am trying to decide whether a machine with multiple CPUs is worth the
>> additional expense performance-wise (aside from being able to assign  
>> CPUs
>
> ??? I cannot believe this is even under consideration. Just how big is  
> your organisation?
>
> I run iptables firewalls on very modest machines, with single and dual  
> T1 lines, and there is never any CPU load from the packet filtering nor  
> the NAT. I don't have any really large sites, but I strongly suspect  
> that iptables firewalling of very large sites could easily be handled by  
> dumpster-grade equipment.
>
> Of course with a budget like yours you'll want something new, which is  
> better (we hope) for the physical reliability of the machine. A fast CPU  
>   is useful for a fast boot time to minimise down time in the event of  
> problems. Otherwise, a waste.
>
> Listen, I ran my home cable, with multiple simultaneous large downloads  
> and 3-4 busy Web browsers on a 386. It never broke a sweat. This of  
> course used ISA 10Mbit NIC's. It could have handled many times the load  
> without problem.
>
> Why did I decommision it? Electricity. I only had so many outlets, and I  
> needed a machine to perform more complex tasks, so the firewall job got  
> handed off to another machine, and the 386 was retired. Still here in  
> case I need it again.
>
> I need a new computer ATM. How about I build a firewall machine for you,  
> and you send me that SMP super machine? ;)

This of course seems to me like a stupendous statement. OK? If your  
firewall is hit by 3000 packets per minute - that's not a great load  
issue. But imagine you have 30000 clients you need to NAT and route.  
That's awful lotta power and you don't have to underestimate the chance of  
you CPU not handling them. I've seen such situations in many ISP's.Their  
routers(x86) just can't handle the traffic. And the dude one step before  
in the thread asked you the right question anyway : Just how big is your  
organisation? Measure your traffic! If it is less than 200-300 mbit/s you  
should not be worrying. If it's more and you have some intense  
services(IDS's , slow-rule traversal,because of many rules,multiple  
servers on each machine), that's when you shall invest your $$$ in BIGGER  
machines. Indeed linux handles SMP almost perfectly, same for HT, but both  
of them is not a good idea(2x2 Xeons for example), because of the  
inconvinience of the posix threading model and the lack of specialized  
support for this type of process queuing.

-- 
www.supportivo.org

I can't stop myself checking for pigs in the outlets. Everybody thinks i'm  
a punk, cause of the hairstyle(220V).
end


  reply	other threads:[~2005-06-03 12:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-02 22:21 iptables on multiple CPUs (SMP & Hyperthreading question) Michael Buffer
2005-06-03  2:15 ` /dev/rob0
2005-06-03 12:12   ` Sertys [this message]
2005-06-04 17:08 ` Mogens Valentin
  -- strict thread matches above, loose matches on Subject: below --
2005-06-03  4:05 Gary W. Smith

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=opsruyzzkd76nf2y@xonix \
    --to=sertys@supportivo.org \
    --cc=netfilter@lists.netfilter.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.