From mboxrd@z Thu Jan  1 00:00:00 1970
From: Marek Kierdelewicz <marek@piasta.pl>
Date: Wed, 14 Nov 2007 21:36:29 +0000
Subject: Re: [LARTC] Hardware Requirements for qdisc htb/sfq
Message-Id: <20071114223629.3f00537b@catlap>
List-Id: <lartc.vger.kernel.org>
References: <7C454E01C5FAE748BEFE65F4C6B7FD8BF42B1F@s-marcell.hemc.coop>
In-Reply-To: <7C454E01C5FAE748BEFE65F4C6B7FD8BF42B1F@s-marcell.hemc.coop>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: lartc@vger.kernel.org

>My question is what are the general hardware requirements for routing
>to about 20 subnets (class c), traffic shaping for about 50 fiber
>customers (TC QDISC), 2 T1s (straight into the Linux router) and about
>35MB of traffic out to the next ISP? We are planning to implement BGP
>sometime in the near future.

>From my experience router load is mostly dependant on pps (packet per
second).

I was doing statefull 550k pps on Athlon64 X2 5200
cpu usage was ~50% per core.

I'm doing stateless > 1m pps on Quad-core Xeon(R) CPU E5345 @ 2.33GHz,
peak cpu usage is less then 25% per core 

both configs used e1000 nics, 1GB Ram
both boxes were running BGP

>I have been searching everywhere for some kind of guidelines, but I see
>none. If anyone could give me a round about answer that would point me
>in the right direction I would be obliged.

Use irqbalance of smp affinity to distribute irqs between cores. Make
your router stateless or optimeze netfilter settings related to
conntrack (more memory, bigger hashtables ect)

>2.0GHz Dual-Core Xeon, 4GB 667MGz RAM, 2x1Gbit Network Interfaces.

Quite a lot of ram for statefull firewall + BGP (1GB would probably
suffice). As for CPU diagnose your network and compare your pps with the
numbers and platforms I specified.

cheers,
Marek Kierdelewicz
KoBa ISP
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc